Fixed
Status Update
No update yet.
Comments
kl...@google.com
ap...@google.com
We have some support in androidx.compose.ui.autofill
Leaving this bug open in case Ralston wants to add more info
pr...@google.com
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
Sometimes we will get flaky test failures in Espresso when running code like the following:
composeTestRule.waitUntilExactlyOneExists(hasTestTag("someTag")).assertIsDisplayed()Similarly, we will also see flaky failures when trying to click on a node:
composeTestRule.waitUntilExactlyOneExists(hasTestTag("someTag")).performClick()The
performClickcall will execute, yet nothing will happen.Adding manual calls to
android.os.SystemClock.sleep(), and/or using a while loop to repeatedly runassertIsDisplayedaddresses the issues for us but I believe there should be a public API for this.Link to kotlinlang Slack discussion: