Status Update
Comments
d-...@mercari.com <d-...@mercari.com> #2
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
gr...@google.com <gr...@google.com>
gr...@google.com <gr...@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.
na...@google.com <na...@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
Repro on Android:
git clone git@github.com:android/compose-samples.git
cd compose-samples/Jetchat
git checkout compose-latest
./gradlew installDebug
TextField
(I used vysor.io)Repro on Desktop:
git clone git@github.com:JetBrains/compose-jb.git
cd compose-jb/examples/widgets-gallery
gradle.properties
and setkotlin.version=1.7.10
compose.version=1.2.0-alpha01-dev770
./gradlew run
Issue in compose-jb:https://github.com/JetBrains/compose-jb/issues/565
Stacktrace: