Fixed
Status Update
Comments
th...@google.com <th...@google.com> #2
We have some support in androidx.compose.ui.autofill
Leaving this bug open in case Ralston wants to add more info
kl...@google.com <kl...@google.com>
ap...@google.com <ap...@google.com> #3
I found an example
D/Autofill Status: Autofill popup isn't shown because autofill is not available.
Did you set up autofill?
1. Go to Settings > System > Languages&input > Advanced > Autofill Service
2. Pick a service
Did you add an account?
1. Go to Settings > System > Languages&input > Advanced
2. Click on the settings icon next to the Autofill Service
3. Add your account
Is this a bug on your side or do the app developers of these password managers need to change their implementation?
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