NatashaDawra / gtalksms

Automatically exported from code.google.com/p/gtalksms
0 stars 0 forks source link

[Market] SQLiteException onUpgrade() "table key_value_already exists" #176

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
GTalkSMS v2.2.3

Java.lang.RuntimeException: Unable to start service 
com.googlecode.gtalksms.MainService@40663180 with Intent { 
act=com.googlecode.gtalksms.action.TOGGLE 
cmp=com.googlecode.gtalksms/.MainService }: 
android.database.sqlite.SQLiteException: table key_value already exists: CREATE 
TABLE key_value (key TEXT NOT NULL, value TEXT NOT NULL, PRIMARY KEY(key))
at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:2173)
at android.app.ActivityThread.access$2800(ActivityThread.java:123)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1002)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:3835)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:507)
at 
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
at dalvik.system.NativeStart.main(Native Method)
Caused by: android.database.sqlite.SQLiteException: table key_value already 
exists: CREATE TABLE key_value (key TEXT NOT NULL, value TEXT NOT NULL, PRIMARY 
KEY(key))
at android.database.sqlite.SQLiteDatabase.native_execSQL(Native Method)
at android.database.sqlite.SQLiteDatabase.execSQL(SQLiteDatabase.java:1763)
at 
com.googlecode.gtalksms.databases.DatabaseOpenHelper.onUpgrade(DatabaseOpenHelpe
r.java:75)
at 
android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.ja
va:132)
at com.googlecode.gtalksms.databases.Database.<init>(Database.java:14)
at com.googlecode.gtalksms.databases.MUCDatabase.<init>(MUCDatabase.java:17)
at com.googlecode.gtalksms.databases.MUCHelper.<init>(MUCHelper.java:22)
at com.googlecode.gtalksms.databases.MUCHelper.getMUCHelper(MUCHelper.java:27)
at com.googlecode.gtalksms.xmpp.XmppMuc.<init>(XmppMuc.java:50)
at com.googlecode.gtalksms.xmpp.XmppMuc.getInstance(XmppMuc.java:71)
at com.googlecode.gtalksms.XmppManager.<init>(XmppManager.java:131)
at com.googlecode.gtalksms.XmppManager.getInstance(XmppManager.java:149)
at com.googlecode.gtalksms.MainService.onStartCommand(MainService.java:386)
at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:2160)
... 10 more

Original issue reported on code.google.com by Florent....@gmail.com on 21 May 2011 at 3:30

GoogleCodeExporter commented 8 years ago
I am curious about the upgrade path the user in this case has taken and if 
others are also experiencing this. Not sure if we should mask this with an 
catch. But if so, we have to at least parse the SQLiteException for "table xyz 
exists". If this is not a widespread issue, I would leave the code as it is.

Original comment by fschm...@gmail.com on 21 May 2011 at 3:44

GoogleCodeExporter commented 8 years ago
Not reproduced on market: I'm closing this bug

Original comment by Florent....@gmail.com on 10 Jun 2011 at 10:50