Jelle Fresen

Seems to be the same issue as in https://stackoverflow.com/questions/65112750/android-test-with-activityscenariorule-hanging-forever

Also, some commenters on https://github.com/android/android-test/issues/676 seem to be running into this issue. Indeed, when changing the launchMode to singleTask as per https://github.com/android/android-test/issues/676#issuecomment-896067367, the test terminates immediately after execution.

@brettchabot Do you have an idea what might be causing this?

Hi. Yes, our focus has shifted to Jetpack Compose indeed. If you are planning to migrate to Compose, that is probably the best option for you.

Compose effects are fully controlled by the MainTestClock, so there should be no possibility for a race there. > The test fails on this line: > > ``` > composeTestRule.setContent...

I see. That could be an indication that you have a self-invalidating loop somewhere in your code. Could you try and add an apply observer to your test like in...

Hi, apologies for replying late. I don't see any obvious repeating pattern in the mutated state, so it looks like there's no self-invalidating loop - at least not state-wise. Is...

> Looper.setMessageLogging(Printer) doesn't compile. Well, you'll need to feed it a Printer As for the timestamps, I was kinda hoping you'd replace your stderr output with logcat output, which formats...

> Pardon my ignorance. I never use loopers or printers, any gist for this? To print to logcat: `Looper.getMainLooper().setMessageLogging { line -> Log.v("TEST_TAG (or anything that helps you identify the...

Here is a minimum project setup that repros the problem. (JDK 17+) [issue-1352-repro.tar.gz](https://github.com/android/android-test/files/14618851/issue-1352-repro.tar.gz) The root cause is that Hamcrest 2.2 is not binary compatible with 1.3. Several overloads were removed,...