I'd like more insights in my coroutine stacktraces of production crashes on Android. I use Firebase ...

# coroutines

[Erik]

I'd like more insights in my coroutine stacktraces of production crashes on Android. I use Firebase Crashlytics) and I came across: https://kotlin.github.io/kotlinx.coroutines/kotlinx-coroutines-debug/

On Android it seems hard to make this work. I added the coroutines-debug dependency, the aspectj-gradle-android plugin and in my application onCreate I call DebugProbes.install(). Running the app leads to an immediate crash about java.lang.NoClassDefFoundError: Failed resolution of: Lcom/google/android/gms/common/R$string. 😞 (Note that I don't even need to call DebugProbes.install(), so the issue lies elsewhere).

Has anybody got experience with debugging Android coroutine stacktraces in production, or any other tips on how to do this?

[gildor]

Unfortunately, Android runtime does not support Instrument API necessary for kotlinx-coroutines-debug to function

[gildor]

What exactly you want to improve? Standard coroutine debug already improves stacktraces, what is your exact problem?

[Erik]

I want to see the files and line numbers in my code base that lead to the point of crash. However, by default (no debugging), the stack traces show all kinds of coroutine internals being called. That makes sense, but is not helpful.

[Erik]

What do you mean by 'standard coroutine debug'?

[gildor]

https://github.com/Kotlin/kotlinx.coroutines/blob/d7de5f5ba66a8d005e5cbd03b18522112303fd54/docs/debugging.md#debug-mode

[Erik]

Is that simply enabled by setting it e.g. through some line in a Gradle script or properties file?

[gildor]

It can be enabled either by setting system property DEBUG_PROPERTY_NAME

[gildor]

not in properties file

[gildor]

you are on Android, so the easiest way is just set it on runtime on App start:

System.setProperty(DEBUG_PROPERTY_NAME, DEBUG_PROPERTY_VALUE_ON)

[Erik]

Thanks. I did that already, but I want sure if that was a common way of doing it. Thanks for the help!