sqlite exception unable to open database file #6193
Comments
cc: @friedbunny as this might be related to #5796 |
|
This was reported last week in #5651, though that was originally an iOS ticket from a month ago. I’m not familiar enough with Android to say whether or not #5796 could cause this crash in the demo app, but if changing the schema was the trigger I would also expect other apps to crash with fresh 4.2.0-beta.2 installs (and that doesn’t appear to be the case so far). iOS hasn’t seen any reports of this crash since 3.3.0 and we haven’t seen it ourselves in iosapp or elsewhere since the database changes. @cammace, try reverting #5796 and see if that fixes the crash. |
|
Building off of my comments in #5651, although I can't consistently reproduce the crash in my own app, I still do get this same crash intermittently. The demo app still crashes every time. |
|
Note that this issues reproducible in the testapp also. |
|
Also reproduce this crash with the 4.2.0 snapshot version : Device : Sony Z5 Compact (Android 6.0) I systematically reproduce the crash when I :
By chance I didn't publish my app update, so I think that I will downgrade to the 4.1.0 version. |
|
I'm switching between style urls in my app and hitting this bug pretty quickly panning and switching styles, even after a fresh install (i.e. no killing of app involved). Can't even demo our app without crashes. (Using Nexus 5X with Android 7.0). |
|
If I add a 200ms delay to the server returning the style, I don't see the crash, or at least I haven't been able to reproduce it yet. |
|
Am seeing this exception as well, using 4.2.0-beta.2 |
|
Seeing this too, even after deleting and reinstalling the app. |
|
I can’t reproduce this crash in testapp or demoapp using the emulator (API 23, Nexus 5X) and I do not have access to any physical devices. Any additional steps/tips/incantations would be much appreciated. For someone who can reproduce this crash, it would be very helpful if you could run a build with #5796 reverted. |
|
We are getting the same crash on Android, it seems that it begins only after some launches. Like it works fine, works fine, works fine, then after some launches, boom, starts crashing. Not even sure what the heck. We are using a custom style. Using "com.mapbox.mapboxsdk:mapbox-android-sdk:4.2.0-SNAPSHOT" |
|
I'm using a custom style too |
|
I seem to get this crash consistently and immediately when going to a certain location (San Jose, CA). When I'm panning and zooming in another part of the world, for instance, the crash is more intermittent. |
|
@tobrun bisected and landed upon 74f094f — the WAL commit. 🙇 That means we should treat this issue as separate from the same SQLite exception seen on iOS in #5651. This thread on the SQLite mailing list sounds suspiciously similar to the problems we’re seeing on Android with WAL and it suggests some solutions. The next step here is #6267 — implementing a custom SQLite error logging function that will give us more information about these exceptions. |
|
Who has solved this problem E/libc++abi: terminating with uncaught exception of type mapbox::sqlite::Exception: unable to open database file |
|
Same error. 09-08 09:28:38.385 32163-32548/digen.bodarider A/libc: /Volumes/Android/buildbot/src/android/ndk-r12-release/ndk/sources/cxx-stl/llvm-libc++abi/libcxxabi/src/abort_message.cpp:74: void abort_message(const char *, ...): assertion "terminating with uncaught exception of type mapbox::sqlite::Exception: unable to open database file" failed |
|
Exact same error as the person right above me. |
Thanks @friedbunny. I read through the thread and one of the things they recommend is to check if the app has permissions to create the We're gonna need to wait for logging to be added to be able to get more information. |
|
SQLite error logging has landed in #6291 and we’ll see if that sheds any new light on this exception. |
|
Fresh databases don’t crash, but The extended logging for this crash looks essentially identical to the thread I linked to earlier where the app doesn’t have permission to write to a temporary folder. Next step: try explicitly forcing SQLite to use the app’s cache directory. |
|
so guys, is there a solution for this: |
|
I have the same problem in Android, is there a solution ? |
|
I think you will release 4.2.0-beta.3 version soon, isn't it? |
|
@friedbunny, Is the fix for this issue available? If so, how do we get it? |
|
@ahuang13 The fix is now available in the latest SNAPSHOT of the SDK, and it'll also be available in the next |
|
Hello everyone |
|
@Burhan-Picon Thanks for the report. You can also update to the latest |
|
@Burhan-Picon : I am also facing the same problem in my App. Can you explain me what all data needs to be cleared to solve this problem ? |
|
@pallavis-webonise to help us resolve this problem, it'd be great to get a copy of the database on the device that you're seeing this crash on, as well as the Mapbox SDK version number you're using. You can find the database in your app bundle at |
|
@kkaefer Thanks for the quick response but we are unable to reproduce this crash on our devices.I am using Mapbox v3.3.7 . I am attaching a crash log we got from crashlytics. I would be very thankful if you can help me out in this. |
|
@pallavis-webonise Thanks for the crash log — you’re seeing #6205, which is a separate issue from this that hasn’t been resolved yet. |
|
@pallavis-webonise the problem is that when you try app for multiple number of times its data become increases and after certain limit it get starts crashing whenever you open map. |
|
@Burhan-Picon : You mean we need to clear cache of Mapbox right ? |
|
Clear cache will not solve this issue. |
|
Please update @Burhan-Picon or open a new ticket with additional information. This issue has been resolved starting with |
|
@cammace I still seem to run into this error with map box 3.4.0 on iOS |
|
Sorry to revive an old thread, but I am getting this issue in 6.4.0 (on Android)
|
|
@evbarnett Could you open a separate ticket about this error and add any other information you have to help us reproduce the issue (device, Android OS version, code snippet...). Thanks! |
|
@evbarnett this crash has been solved in #12224, which is part of Android 6.5.0 and newer. Please upgrade to this version. |
|
@zugaldia Thanks for replying- I did open a separate ticket the same day @kkaefer Thank you, I'll give the new version a try. |
Updated the demo app to
4.2.0-beta.2on Thursday and have had issues with crashing since. Clearing the app data will resolve the issue temporarily but after sometime, opening the app again and clicking an example will result in the crash again. I think this issue might have been introduced in PR #5796.cc: @mapbox/android
The text was updated successfully, but these errors were encountered: