Android sqlitecantopendatabaseexception unable to open database file

SQLiteCantOpenDatabaseException: unable to open database file (code 14): , while compiling: PRAGMA journal_mode #251

Comments

robertoestivill commented Aug 27, 2017

I got several reports on firebase about the following triggered by the Snowplow SDK.
Any workaround?

• VM free: 1.25MB
• VM total: 11.41MB
• VM max: 64MB
• Battery level: 15%
• Charging state: Unplugged
• Connection State: Wwan

• Manufacturer: Samsung
• Model: GT-I9300
• Board: Smdk4x12
• Android API: 18
• Android OS: 4.3
• Brand: Samsung
• RAM: 831.05MB
• Orientation: Portrait

The text was updated successfully, but these errors were encountered:

BenFradet commented Aug 28, 2017

Could it be caused by multiple calls to EventStore.open ?

robertoestivill commented Aug 28, 2017 •

Hi @BenFradet ! I don’t know the internals of the sdk, but I can tell you that’s not our case.
The Emitter is only initialized and referenced from an AnalyticsWrapper class that gets instantiate as a Dagger singleton. So at first sight, there’s no chance we are initializing the Emitter twice.

jbeemster commented Aug 28, 2017

Hey @robertoestivill could you please add the version of the tracker you are using and the code that actually instantiates and sets up the tracker?

robertoestivill commented Aug 28, 2017 •

quiro91 commented Nov 3, 2017

I’m experiencing the same issue in version 0.6.2, any news about it?

alexanderdean commented Nov 3, 2017 •

Hey @quiro91 could you please add the code that actually instantiates and sets up the tracker?

quiro91 commented Nov 6, 2017 •

@alexanderdean version 0.6.2, here’s the code:

alexanderdean commented Nov 6, 2017

Thanks @quiro91! We will investigate.

ablenesi commented Aug 31, 2018

We are also experiencing the same issue

alexanderdean commented Aug 31, 2018

Thanks, assigning to @mhadam to take a look.

mhadam commented Sep 4, 2018

@ablenesi do you have any information about the system where this happens? I’m mostly interested in which version of Android.

ablenesi commented Sep 5, 2018

Happened on a OnePlus One, Android 6.0.1 — Only this single user was affected, the crash happened 26 times.

mhadam commented Sep 5, 2018

I wonder if this issue is related to external storage or write access privileges.

anujmiddha commented Jan 9, 2019

We have the same issue. Our Crashlytics statistics —

Device distribution is across Samsung, Motorola, Lenovo and others.
OS distribution is across versions 5, 6, 7 and 8.
90% of the devices are in background

jayabrown commented Dec 20, 2019 •

We are also experiencing this issue, happening only on Moto e5 play.

StayZeal commented Jun 12, 2020 •

android 6.0
only one device
mylog:

Источник

Crash: android.database.sqlite.SQLiteCantOpenDatabaseException: #1436

Comments

ReCursia commented Apr 8, 2020

[READ] Step 1: Are you in the right place?

Issues filed here should be about bugs in the code in this repository.
If you have a general question, need help debugging, or fall into some
other category use one of these other channels:

• For general technical questions, post a question on StackOverflow
  with the firebase tag.
• For general Firebase discussion, use the firebase-talk
  google group.
• For help troubleshooting your application that does not fall under one
  of the above categories, reach out to the personalized
  Firebase support channel.

[REQUIRED] Step 2: Describe your environment

• Android Studio version: 3.6.1
• Firebase Component: i have problem in /transport directory
• Components versions:
  firebaseCloudMessaging 20.1.0
  firebaseStorage 16.0.1
  firebaseConfig 16.1.0
  firebasePerfomance :19.0.5

[REQUIRED] Step 3: Describe the problem

Steps to reproduce:

I have crashes SQLite for Android version >= 7
I do have
in AndroidManifest.xml.
Does it write to external storage or it uses internal storage?

Relevant Code:

The text was updated successfully, but these errors were encountered:

google-oss-bot commented Apr 8, 2020

I couldn’t figure out how to label this issue, so I’ve labeled it for a human to triage. Hang tight.

ashwinraghav commented Apr 9, 2020

Hi!
Can you clarify what it is that you are trying to accomplish ? Are you building the project from source while trying to make a contribution?

ReCursia commented Apr 10, 2020

I’m using this Firebase SDK library in my Android application.

fpittersacc commented Apr 12, 2020

We are also seeing the same stacktrace on GPlay Publish, happening only on a Philips 4K ((PH7M_EU_5596) with Android 8.0

Using the latest version:
firebase_core = ‘17.3.0’
firebase_perf = ‘19.0.6’
firebase_messaging = ‘20.1.5’
firebase_links = ‘19.1.0’

vkryachko commented Apr 14, 2020

From the above it’s hard to see the underlying issue, does the exception have a «caused by» chain and or the error message?
@ReCursia @fpittersacc

fpittersacc commented Apr 14, 2020

Hi @vkryachko, sadly there is no further information on Google Play Publish, and is not reported to Firebase, so it’s probably happening at launch, at the very beginning?

Although we are seeing that crashes are happening on groups:

6 at the same time (only hours and minutes on GPlay), which could potentially mean that above logic is being hit too often?
We are trying to trace down on which cases above logic is reached, but any help or guidance is appreciated.

vkryachko commented Apr 14, 2020

I see, that makes sense. Unfortunately it seems like a known issue in the Play Console. i.e. lack of any details in the stacktrace makes the stacktraces useless in terms of helping diagnose the problem 🙁

Any steps to repro would be greatly appreciated as we don’t have that hardware available for testing at this time

vkryachko commented Apr 14, 2020

@fpittersacc alternatively I would suggest trying to install com.google.firebase:firebase-crashlytics:17.0.0-beta01 and seeing if a more detailed crash lands into the Firebase Console.

fgl27 commented Apr 18, 2020 •

I also have this

The above is all that play console shows.

It only happens to Android 8.0 devices, and stated after I enable crashlytics plugin
I have crashlytics-gradle 2.0.0-beta04 and crashlytics 17.0.0-beta04 enable

No reports arriving at the firebase console about this only on play console, so I assume that is firebase crashing for some reason.

Device is the same as @fpittersacc posted about
Philips 4K LED TV powered by Android (PH7M_EU_5596), 2048MB RAM, Android 8.0
plus
Sony BRAVIA 4K GB (BRAVIA_ATV2), 1792MB RAM, Android 8.0
Sony BRAVIA 4K GB ATV3 (BRAVIA_ATV3_4K), 1792MB RAM, Android 8.0

I don’t own any of those can help with device testing.

I didn’t received any user reporting that the app stopped working so it may only be a firebase crash and the app keeps working or maybe the user just install the app it didn’t work so unistall don’t know for sure yet.

fgl27 commented Apr 20, 2020 •

About the above commit, I have 75+ crashes on play console after enabling the crashlytics plugin, only 2 showed in firebase console.

63 of those crash on play are from android.database.sqlite.SQLiteCantOpenDatabaseException:

So there is at least 10 missing from firebase so it is not working for me at all.

After a few days I report back with the result of not having the plugging enable.

vkryachko commented Apr 20, 2020

@fgl27 the issue is that it’s not possible to repro android.database.sqlite.SQLiteCantOpenDatabaseException plus it is missing the underlying problem. All it tells is that the sqlite db was not openable, usually the exception message would reveal the reason it was so.

What I can tell is the on the device in question(PH7M_EU_5596) the os is preventing from writing into/reading from app private storage(which should not require any permission at all), so this is either a bug in the os or the devices is in some misconfigured state.

So to be able to tell more precisely what the cause is, we would need that exception message

fgl27 commented Apr 20, 2020

I understand that I read it before the console is bugged that is why I enable crashlytics.

Also there is others android 8.0 devices affected not just PH7M_EU_5596 , is a 8.0 issue, this is probably a bad implementation of selinux, maybe those device have a earlier version of 8.0 that has a unfinished sepolicy rulles that is prevent the write of a particularly action, I already see issues like this on other devices, maybe is something else on the underline of android permission. As this device is probably deprecated it will not receive Android updates, this issue will not be fixed by the manufacturer so if is something that we can address here will probably help others.

The main problem I have is that enabling the plugin has no result.

As I wrote. after enabling I have 75+ crashes on play console on that particularly version of the app that has crashlytics enable, and only 2 on firebase, it makes no sense to keep a thing that crashes and has no result enabled.

So lets see the result after I disable it.

Maybe someday google goes back and fixes they crash console and we can have a proper log.

The main reason I’m writing here is not to complain is just to post my info and keep my self on the conversation in case there is news on it.

vkryachko commented Apr 20, 2020

I understand that I read it before the console is bugged that is why I enable crashlytics.

Also there is others android 8.0 devices affected not just PH7M_EU_5596 , is a 8.0 issue, this is probably a bad implementation of selinux, maybe those device have a earlier version of 8.0 that has a unfinished sepolicy rulles that is prevent the write of a particularly action, I already see issues like this on other devices, maybe is something else on the underline of android permission. As this device is probably deprecated it will not receive Android updates, this issue will not be fixed by the manufacturer so if is something that we can address here will probably help others.

The change I made above will help mitigate the problem, i.e. it will not crash the app(to be released in the coming weeks), but I imagine any app or sdk that uses sqlite will not work on such devices, which is a big deal imo.

The main problem I have is that enabling the plugin has no result.

This is because the new crashlytics(com.google.firebase:firebase-crashlytics) depends on datatransport for crash delivery, and datatransport is what is failing to initialize.

To debug this further, one thing you could try doing is:

1. Configure the old crashlytics sdk com.crashlytics.sdk.android:crashlytics:2.10.1
2. Add the following dependency to your app com.google.firebase:firebase-datatransport:17.0.3
3. At app start call TransportRuntime.initialize(getApplicationContext());

this will make sure the crash is delivered to Firebase Console and should preserve all the details of the stacktrace.

As I wrote. after enabling I have 75+ crashes on play console on that particularly version of the app that has crashlytics enable, and only 2 on firebase, it makes no sense to keep a thing that crashes and has no result enabled.

So lets see the result after I disable it.

Maybe someday google goes back and fixes they crash console and we can have a proper log.

The main reason I’m writing here is not to complain is just to post my info and keep my self on the conversation in case there is news on it.

Источник

android.database.sqlite.SQLiteCantOpenDatabaseException: unable to open database file #154

Comments

casolorz commented Apr 10, 2015

Just got this over crashlytics. I’m guessing it happened to me because I only initialize Stetho if the app is debuggable but I don’t remember the crash. Anyways I figured I should report it. I am using Stetho 1.1

The text was updated successfully, but these errors were encountered:

jasta commented Apr 11, 2015

Hmm. You must have been inspecting actively in stetho to cause this, correct? I’m really not sure why this would happen in practice tho. I’ll have to dig in a bit when I get back from Droidcon

jasta commented Apr 11, 2015

Looking closer, this can clearly happen due to races (such as removing a database shortly after Stetho begins initialization). We soften this exception in other areas (such as executeSQL) and I think the right call is to soften it for getDatabaseTableNames as well.

casolorz commented Apr 11, 2015

You know I did have some crashes of the Chrome window while I was doing the inspection but I don’t remember the app crashing. Anyways what I did to get those Chrome window crashes is I looked into the preferences of other libraries under the local storage section. I first looked at my own preferences and then I thought, ohh look at all those other preferences, and as soon as I clicked on one of those the window just closed itself.

jasta commented Apr 11, 2015

We’re tracking that with #151 🙂

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

android.database.sqlite.SQLiteCantOpenDatabaseException: unable to open database file (code 14) #348

Comments

Vivecstel commented Jun 22, 2016

Hello 🙂 I am getting the following exception from time to time when doing a lot of read / write on my db. Note that using background threads for db access though :

• com.birbit.android.jobqueue.Job (instead of async task. I use this mostly in fragments to fetch database data or write some quick data in the database)
• android.app.IntentService(to write data in the database)
• android.app.job.JobService(to write/update datain the database)
  So after heavy db usage a sometimes get the following crash :

I use a single dao session that I get from this singleton throughtout the application :

The text was updated successfully, but these errors were encountered:

Vivecstel commented Jun 25, 2016

Switched to store the dao session to application class instead(not that it makes any difference from singleton) and limiting one background service usage to start only when application closes, seems to do the trick.

aamir2590 commented Nov 14, 2017 •

Even if we have store DaoSession Object in Application class, we are getting this exception. Can you please suggest any solution.

greenrobot-team commented Nov 14, 2017

@aamir2590 This is a SQLite error. I suggest to search for SQLiteCantOpenDatabaseException: unable to open database file on Google. -ut

nAkhmedov commented Oct 29, 2018 •

I am facing this issue too on Android 8

java.lang.RuntimeException:
at android.app.ActivityThread.handleBindApplication (ActivityThread.java:6532)
at android.app.ActivityThread.-wrap2 (Unknown Source)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1963)
at android.os.Handler.dispatchMessage (Handler.java:108)
at android.os.Looper.loop (Looper.java:166)
at android.app.ActivityThread.main (ActivityThread.java:7425)
at java.lang.reflect.Method.invoke (Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run (Zygote.java:245)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:921)
Caused by: android.database.sqlite.SQLiteCantOpenDatabaseException:
at android.database.sqlite.SQLiteConnection.nativeOpen (Native Method)
at android.database.sqlite.SQLiteConnection.open (SQLiteConnection.java:223)
at android.database.sqlite.SQLiteConnection.open (SQLiteConnection.java:207)
at android.database.sqlite.SQLiteConnectionPool.openConnectionLocked (SQLiteConnectionPool.java:511)
at android.database.sqlite.SQLiteConnectionPool.open (SQLiteConnectionPool.java:194)
at android.database.sqlite.SQLiteConnectionPool.open (SQLiteConnectionPool.java:183)
at android.database.sqlite.SQLiteDatabase.openInner (SQLiteDatabase.java:880)
at android.database.sqlite.SQLiteDatabase.open (SQLiteDatabase.java:864)
at android.database.sqlite.SQLiteDatabase.openDatabase (SQLiteDatabase.java:767)
at android.app.ContextImpl.openOrCreateDatabase (ContextImpl.java:820)
at android.content.ContextWrapper.openOrCreateDatabase (ContextWrapper.java:299)
at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked (SQLiteOpenHelper.java:266)
at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase (SQLiteOpenHelper.java:206)

rakhi191 commented Jan 31, 2020 •

@nAkhmedov am facing same issue SQLiteCantOpenDatabaseException in Android 8 Samsung device.
Did you find any solution ?

Источник