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

# compose-android

[Albert Chang]

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.

[Albert Chang]

Okay never mind. Seems that it's already fixed but not yet released.

[ascii]

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

[ascii]

CL is from Oct 19

[Albert Chang]

It's Compose Runtime.

[ascii]

of course, my bad