:android-wave: Anyone an idea how to debug `ComposeContentTestRule.*awaitIdle()*` issues? We have mu...

# compose-android

[Jonas]

👋 Anyone an idea how to debug ComposeContentTestRule.*awaitIdle()* issues?
We have multiple UI tests where it works as expected but some where it is flaky.
I always get to a LaunchedEffect which should trigger a side effect but only rarely get into the Coroutine block of the LaunchedEffect. (Test ends without waiting of completion.)

🔴 (always reached) LaunchedEffect(uiState.registrationProgress) {
🔴 (when both breakpoints: it mostly reaches this debug point in debug mode) ...
🔴 (when only this breakpoints: it rarely reaches) ...

[Zach Klippenstein (he/him) [MOD]]

Which version of compose?

[Jonas]

Tested with androidxComposeBom = "2023.09.02" and "2023.08.00"

[Zach Klippenstein (he/him) [MOD]]

can you file a bug please? I think might be a regression

[Zach Klippenstein (he/him) [MOD]]

And are you running tests on a device or via robolectric?

[Zach Klippenstein (he/him) [MOD]]

i tried a really simple repro case and it behaves the way i’d expect with waitForIdle, but there’s some additional machinery with awaitIdle that might be involved. If you can provide a reproducer when you file the bug, that would be helpful

[Jonas]

@Zach Klippenstein (he/him) [MOD] sry for the late response.
We are testing on a real device.
Finally found the time to make a reproducer:
https://issuetracker.google.com/issues/305049806