The error is printed in the logs when you navigate...

# decompose

[Arkadii Ivanov]

The error is printed in the logs when you navigate or init your navigation on a non-main thread. There should be a stack trace pointing to the offending code.

[Vaibhav Jaiswal]

it pointed to this function

[Arkadii Ivanov]

Yes, but there should also be a trace to the place where that function was called, and so on. It would be helpful if you could post the entire stack trace.

[Vaibhav Jaiswal]

Sorry for the delay
I found out the issue
I was calling navigate from a flow which was on IO dispatcher

[Vaibhav Jaiswal]

Btw is it possible for decompose to change dispatcher internally or an interceptor or something in which i can switch to Main thread?

[Arkadii Ivanov]

Thanks for the update! Currently there is no way to switch threads automatically. But I will think about it, thanks again.

[Vaibhav Jaiswal]

If i by mistake navigate on a non main thread
Will app crash or is it just a warning printed in logs?

[Arkadii Ivanov]

It's just an error in the logs, not a crash.

[Arkadii Ivanov]

You can attach your own interceptor via onDecomposeError gollobal callback and crash the app, or report to an analytics service of your choice.

[Vaibhav Jaiswal]

Ahh i see

I wanted that interceptor to intercept all nav events and move it to main thread

[Arkadii Ivanov]

Yeah, automatic thread switching is not possible right now. This has to be carefully thought through before implementing, as there might be implications.

[Vaibhav Jaiswal]

Ohh i see
Hoping to see it in future Decompose release