A modern programming language that makes developers happier.

kotlinlang

Do you wrap `delay` in try/catch so it doesn't crash if job was cancelled while waiting?

Hopefully not, since the entire purpose of cancellation is to stop computations from continuing! Normally, you should always rethrow a `CancellationException` if you happened to catch it.

We see raise of the JobCancellation exception in crashlytics

Since stacktrace is not helpful, I was looking to the code around it happened

And only things I see is `tryEmit` on channel and `delay` in view model scope

AI says to wrap delay in NonCancellable context

``` coroutineScope {
    val job = launch {
        delay(100.seconds)
    }
    job.cancel()
}```
will not throw an exception. Coroutines don't treat cancellation exceptions as problems.

Something more complex than just `delay` throwing because of a cancellation must be going on.

You're welcome, but we didn't really figure out what's going on. If you'd like, you could share some code so that we could brainstorm a way to restructure it.

Yeah, don't log any CancellationException if you have an exception handler. They are fine.

Eg, our OkHttp (Retrofit) would log these as "Cancelled" over and over again when a network request was suspending. We had to suppress those.

Oke people, thank you so much for guidance. So I tried to look further what happens after even fired and found one more place where runBlocking is called with another view model scope that might be cancelled

I'm checking if the scope needed there at all

&gt; Since stacktrace is not helpful
Taking this opportunity, I'd recommend <https://github.com/reformator14/stacktrace-decoroutinator|Decoroutinator> for full traces.

There is also some movement from JB to make it easier