Jan Skrasek
07/19/2022, 11:38 AMTest instrumentation process crashed.
app simply stops responding to some focus event and then instrumentation timeouts after 5 seconds, what's more, the interaction is on non-compose view at this particular time.
• java.lang.IllegalStateException: No compose hierarchies found in the app. Possible reasons include ...
suddenly this started happening, but not always - probably tests access activity too early, seems like idling resource issue, but this was not happening at all before update
• Compose recomposing forever - timeouting because not able to reach an idle state - this was only issue I was able to fix - we were missing remember
, but actually without UI test no repeated recomposition was happening there
Do you any similar experience, tips where to look for issues/errors/fixes?Paul Woitaschek
10/27/2022, 9:25 AMJan Skrasek
10/27/2022, 9:28 AMTest instrumentation process crashed.
The No compose hierarchies found in the app.
seems to be fixed (don't know why) by this particular change I did yesterday:
• we were using createEmptyComposeRule for our full end-to-end UI tests that were using own ActivityAscenarioRule.
• I've replaced createEmptyComposeRule with this:
@get:Rule
val composeTestRule = AndroidComposeTestRule(activityTestRule) {
error("Can't provide current activity")
The activityTestRule is the activity scenario rule we had there for the whole time.Paul Woitaschek
10/27/2022, 9:42 AMJan Skrasek
10/27/2022, 9:44 AM