When running my android unit test (not instrumented). I get this stack trace printed when trying to set the dispatcher in my setup function. The test passes, but this makes the build output very noisy. Anyone know if I'm doing something wrong. The exception says to call

Dispatchers.setMain

, but that is the function creating the stack trace.

the exception is from

TestDispatchers

not

Dispatchers

I understand how to use

setMain

and I'm trying to use it. What seems to be happening is

setMain

grabs a copy of the current Main to support

resetMain

, but getting the current version fails and that failure gets logged. Is there something that I can do to prevent this behavior.

a code snipped how you use it might help 😉

@Before
    override fun setUp() {
        Dispatchers.setMain(Dispatchers.Unconfined)
        viewportManager.setUp()
    }

    @After
    override fun tearDown() {
        if (this::viewport.isInitialized) {
            viewport.dispose()
        }

        viewportManager.tearDown()
        Dispatchers.resetMain()
    }

The stack trace points to my call of `Dispatchers.setMain(Dispatchers.Unconfined)`

I think you need to use a

TestDispatcher

. here’s how I use it in my projects https://github.com/chrimaeon/curriculumvitae/blob/b3fa2fdc9d47a8f34d3fd9845c948cd8[…]cmgapps/android/curriculumvitae/test/MainDispatcherExtension.kt

I don't think that will make a difference because the

setMain

function doesn't look at the dispatcher type. Trying to run again, but it is no longer printing this stack trace even though I didn't change anything.