Status Update
Comments
da...@google.com <da...@google.com> #2
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
tn...@google.com <tn...@google.com> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
tn...@google.com <tn...@google.com> #4
-
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 <da...@google.com> #5
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
Room recently moved some of its APIs and source from Java to Kotlin and int def enforcement seems to have been lost with the move.
Given the IntDef in Room OnConflictStrategy , wrong usage of it in Kotlin gives no warning:
the enforcement is also lost in Java sources:
However, if I make a new
@IntDef
along with an annotation in Java, the enforcement works fine.Let me know if you need more information!