Status Update
Comments
ap...@google.com <ap...@google.com> #2
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
je...@google.com <je...@google.com> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
no...@google.com <no...@google.com>
si...@google.com <si...@google.com>
si...@google.com <si...@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.
ra...@google.com <ra...@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
The following Experimental APIs have existed for several releases.
Please consider stabilising or removing these APIs:
fe9050830b23compose/ui/ui/api/public_plus_experimental_current.txtctor @androidx.compose.ui.ExperimentalComposeUiApi public PointerInputChange(long idfe9050830b23compose/ui/ui/api/public_plus_experimental_current.txtmethod @androidx.compose.ui.ExperimentalComposeUiApi public androidx.compose.ui.input.pointer.PointerInputChange copy(optional long idfe9050830b23compose/ui/ui/api/public_plus_experimental_current.txtmethod @androidx.compose.ui.ExperimentalComposeUiApi public float getPressure();