I have a bunch of code that (schematically) does t...

# coroutines

[mbonnin]

I have a bunch of code that (schematically) does this:

GlobalScope.launch {
            val deferred = CompletableDeferred<Unit>()

            Thread {
                val result = doSomething()
                if (result == SUCCESS) {
                    deferred.complete(Unit)
                } else {
                    deferred.completeExceptionally(Exception("oopps"))
                }
            }.start()

            deferred.await()
        }

This is working well in the nominal case but in the error case, nothing in the backstack indicates where the await() is done. Is there any chance I could have that info somehow to help debug a crash ?

[mbonnin]

The await are basically scattered in all the codebase and the thread is the okhttp threadpool. I get a crash from firebase reporting but no clue where the missing try/catch is.

[mbonnin]

I'm using the apollo client all over the place and bridging it to coroutines with https://github.com/apollographql/apollo-android/blob/master/apollo-coroutines-support/src/main/kotlin/com/apollographql/apollo/coroutines/CoroutinesExtensions.kt#L81

[mbonnin]

It might be something else but it really looks like I'm missing a try/catch somewhere. Having that info in the crash report would help a lot

[gildor]

Okay, this coroutine adapter looks fine

[gildor]

First of all, did you enable coroutines debug mode? It allows to restore suspension points stack

[gildor]

https://github.com/Kotlin/kotlinx.coroutines/blob/master/docs/debugging.md

[gildor]

Could you share some example of stack trace?

[mbonnin]

ah, cool, didn't know about that. That might help but I'm afraid it won't be enough as so far I haven't been able to reproduce the crash so I was hoping to get some more logs from firebase.

[mbonnin]

Crash look like this: https://gist.github.com/martinbonnin/f75c1791c250347e7734c13a64b0d60f