If I get an exception for a coroutine scope, it’s ...

# coroutines

[enighma]

If I get an exception for a coroutine scope, it’s marked as canceled even with a handler.

What is the best practice to make another call with that scope? since it’s marked canceled my instinct is to create a new one, is that the preferred approach?
I thought the handler would ensure it was not canceled, which doesn’t seem to be the case.

[Sam]

Does this help? https://kotlinlang.org/docs/cancellation-and-timeouts.html#run-non-cancellable-block

[Sam]

try {
    ...
} finally {
    withContext(NonCancellable) {
        // can suspend even after cancellation
    }
}

[enighma]

I did something like:

scope.launch(exceptionHandler) {
}

However, once an exception happens, the scope cannot be used again.

One solution is to add a try-catch inside of the launch{} but I might just not understand how

CoroutineExceptionHandler

is intended to work

[Sam]

CoroutineExceptionHandler happens after the coroutine has completed. It doesn't let you recover from the exception. https://kotlinlang.org/docs/exception-handling.html#coroutineexceptionhandler

[enighma]

ah! yeah, that helps explain the situation then 🙂 Thanks for pointing that out!

[ildar.i [Android]]

You can run your coroutines inside SupervisorJob. It doesn't cancel if one of its children cancel