Status Update
No update yet.
Comments
kl...@google.com
kl...@google.com
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
an...@google.com
va...@google.com
ap...@google.com
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
hi...@gmail.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.
va...@google.com
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
Currently
AndroidComposeViewreads a system property to determine whether the developer option "Show layout bounds" has been enabled, and if so, every layout node draws its bounds. But we only read that value from the system when the lifecycle hosing the ACV is resumed. When the setting is changed from a quick settings tile, the activity is never paused, so it won't pick up the new setting. Android Views behave as expected: When the quick setting tile is toggled, they immediately start drawing their bounds. Compose should do the same.There is an API for registering for property changes that we might be able to use:https://cs.android.com/android/platform/superproject/+/master:frameworks/base/core/java/android/os/SystemProperties.java;l=244;drc=fcdba12869220502f025217077317251155d152f