Status Update
No update yet.
Comments
da...@google.com
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
to...@gmail.com
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
ap...@google.com
-
Second crash in the description is from a real device. Experienced it myself on two different Xiaomi phones, plus lots of crashes from users in the Google Play console.
-
Dynamic features are not used in the application.
As a wild guess, I have downgraded build tools from 31.0.0 to 30.0.3, compileSdk from 31 to 30, and moved all work with Language ID to the service in a separate process (just to be sure that crash can kill secondary process instead of main). This combination is in beta for 2 days by now and I don't see any SIGSEGV crashes.
da...@google.com
Hmm, I feel the crash might be something related to separate/secondary process.
I also changed compileSdk and targetSDK to 31 but still cannot repro this issue.
Description
Android 7.1
Room 2.1.0 works well, but failed on 2.2.0-alpha01
This happened on an update sql with 3 param's placeholder but 2 of them are the same, maybe this info is helpful.
```
java.lang.IllegalArgumentException: Cannot bind argument at index 3 because the index is out of range. The statement has 2 parameters.
at android.database.sqlite.SQLiteProgram.bind(SQLiteProgram.java:212)
at android.database.sqlite.SQLiteProgram.bindString(SQLiteProgram.java:166)
at androidx.sqlite.db.framework.FrameworkSQLiteProgram.bindString(FrameworkSQLiteProgram.java:50)
at one.mixin.android.db.MessageDao_Impl.takeUnseen(XXXDao_Impl.java:1186)
at one.mixin.android.db.DaoExtensionKt$batchMarkReadAndTake$1.invoke(DaoExtension.kt:104)
at one.mixin.android.db.DaoExtensionKt$batchMarkReadAndTake$1.invoke(DaoExtension.kt)
at one.mixin.android.db.XXXDatabaseKt$sam$java_lang_Runnable$0.run(XXXDatabase.kt)
at androidx.room.RoomDatabase.runInTransaction(RoomDatabase.java:391)
```