After I upgraded compose to latest alpha, all host-side tests that are using

mutableStateOf

started to fail with

java.lang.RuntimeException: Method getMainLooper in android.os.Looper not mocked

thrown in

androidx.compose.runtime.ActualAndroid_androidKt.<clinit>

. While I understand the motivation of the change, I'm wondering if it makes sense to make

MainThreadId

fallback to -1 gracefully so that the user don't have to update every test or use

unitTests.returnDefaultValues = true

, since this is a really common use case.

Am I reading it wrong? Isn't this fix included in the latest Compose Compiler release?

It's Compose Runtime.

of course, my bad