Fixed
Status Update
No update yet.
Comments
al...@google.com
A couple of questions:
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
jb...@google.com
ap...@google.com
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
jb...@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.
Description
ViewModelProviderKtexists in bothlifecycle-viewmodel-ktx:2.3.1, which gets pulled in transitively byappcompat, andlifecycle-viewmodelat head. If I updateappcompattolifecycle-viewmodelit's going to cause a classpath conflict for a lot of external clients.Dependency constraints should be used here, but Gradle has several bugs in dependency constraint resolution that prevent us from using it (seehttps://github.com/gradle/gradle/issues/19882 ).
Please use a different
JvmNamefor the class inlifecycle-viewmodelso that we can avoid the conflict without needing to blocklifecycle-viewmodelorappcompat's release on Gradle fixing their bugs.