Status Update
Comments
se...@google.com <se...@google.com> #2
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
jb...@physitrack.com <jb...@physitrack.com> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
ap...@google.com <ap...@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.
se...@google.com <se...@google.com>
ar...@physitrack.com <ar...@physitrack.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
Jetpack Compose version: BOM 2023.09.00 Jetpack Compose component used: Material3 Android Studio Build: #AI-223.8836.35.2231.10671973 Kotlin version: 1.9.10
Steps to Reproduce or Code Sample to Reproduce:
Please see attached screenshot