what is the best way to track down something like this? (android app)

ime  D  Shutting down VM
     E  FATAL EXCEPTION: main
     E  Process: com.dhl.lps.consumer.debug, PID: 18730
     E  kotlinx.coroutines.JobCancellationException: Job was cancelled; job=StandaloneCoroutine{Cancelling}@48c8a44

we have scopes like

MainScope() + CxExceptionHandler(..)

with

launch { .. }

consistently. no

async

for now. so this seems to be some weird/interesting edge case.. 🙂 any pointers on how to track this thing down? 🤔

Complete stacktrace would be a great start 🙂 But most likely it is an interopability issue: all coroutines machinery generally ignores

CancellationException

. Probably you do something like

Channel.offer

from within a callback and do not catch CE

been debugging this all day.. it seems like it is caused by cancelling a job that contains a flow - but cancelling from within the collect body of the flow itself.. so.. not cancelling the flow from within itself.. but its surrounding job.. this randomly but most of the time crashes the app by letting the cancellation exception escape.. like.. it slips by the installed top level exception handler of the scope.. sounds weird to bad.. 😕 but still debugging..