Fixed
Status Update
No update yet.
Comments
kl...@google.com
ap...@google.com
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?
pr...@google.com
Tested on Android 12 Emulator with custom executor, but cannot repro this issue.
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: