When writing a compose UI test on a Composable, is there a simple of way finding out what is causing a ComposeNotIdleException? The composable seems to work fine when you use it in the app and layout inspector doesn’t flag any issues w/ it…
It would be nice if there were some way to print out which composable is recomposing and the input causing it to w/ some sort of debug flag on composeTestRule.