I found that if I don't include a ComponentActivity in my AndroidManifest, then using createComposeRule() means that test stalls and eventually bombs out with "activity never becomes requested state "[destroyed, resumed, created, started]"
I wonder would it be better to have a more explicit exception message here, as it took me quite a while to figure out what I'd done wrong? Something like "ComponentActivity not found - have you included it in your AndroidManifest?".
08/04/2020, 10:43 AM
It would also be nice if we would only have to add the