Status Update
Comments
al...@jetbrains.com <al...@jetbrains.com> #2
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
se...@google.com <se...@google.com>
as...@google.com <as...@google.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.
si...@gmail.com <si...@gmail.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: 1.5.5-dev-k2.0.0-Beta1-06b8ae672a4
Jetpack Compose component(s) used:Android Studio Build:Kotlin version: 2.0.0-Beta1
Steps to Reproduce or Code Sample to Reproduce:
Seehttps://youtrack.jetbrains.com/issue/KT-63722 . I believe the issue is in Compose rather than in Kotlin, so reporting it here.
Stack trace (if applicable):