Fixed
Status Update
Comments
ti...@google.com <ti...@google.com>
je...@google.com <je...@google.com> #2
A couple of questions:
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
1. Have you saw crash in real device or only in simulators?
2. Do you use dynamic feature for language ID?
cl...@google.com <cl...@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.
Description
Jetpack Compose version: 1.8.0-alpha08
Jetpack Compose component(s) used: ui-test
Just looking at the API, I would enable a11y checks as follows:
However this is not how the API was designed to be used because
enableAccessibilityChecks
creates a newAccessibilityValidator
ui-test-android-1.8.0-alpha08.../androidMain/androidx/compose/ui/test/ComposeUiTest.android.kt
Actually, this code:
would not work as expected either, as the validator would be replaced when the checks are enabled.
The correct snippet would be
We can definitely document this well, but I'd like to discuss if the API should be improved.
For example
enableAccessibilityChecks()
->enableAccessibilityChecks(accessibilityValidator: AccessibilityValidator = accessibilityValidator())
and make the setter for
accessibilityValidator
private.