That is interesting, but why does it only happen in a seemingly random
fashion? Say, one out of every 1 app launches ?
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to
Kinda sounds like a race condition between SQLiteOpenHelper and onCreate...
maybe?
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send
I see a handful of these in my Dev Console error logs, but have never had it
happen somewhere I can chase it down. Here's a typical stack trace:
android.database.sqlite.SQLiteException: unable to open database file
Caused by: android.database.sqlite.SQLiteException: unable to open database
file
I get the occasional crash report that
android.database.sqlite.SQLiteException: Can't upgrade read-only database
from version 0 to 1
which is totally bogus and might be in the same league as your issue
--
You received this message because you are subscribed to the Google
Groups Android
FWIW, SQLiteOpenHelper treats version 0 as the initial state, where the
DB exists, but onCreate hasn't been called yet.
getWritableDatabase:
int version = db.getVersion();
if (version != mNewVersion) {
db.beginTransaction();
try {
5 matches
Mail list logo
