Fixed
Status Update
Comments
th...@google.com <th...@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?
kl...@google.com <kl...@google.com>
ap...@google.com <ap...@google.com> #3
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
na...@google.com <na...@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
I was unable to assert state change during unit test using espresso view matchers like so:
where SomeComposable contains an AndroidView composable that has an update block depending on a state created inside the composable.
Example of when it doesn't work in unit test -- creating the state where the composable wraps around the AndroidView()
Example of when it does work -- pushing the state delegation to another composable and having the AndroidView-wrapping Composable only accept the final string returned from state