Reading deobfuscated stack trace reports in Play console

I have a stack trace in my Play app (fortunately, it’s alpha testing) that doesn’t look like it’s a valid codepath through the source. Do I have to take these stack traces with a grain of salt?

I guess Proguard can transform the code, and Kotlin generating JVM classes may not match up so well. But in this stack trace I see this juggle between 2 functions, that don’t call each other. I was just hoping there’s a good way to tell which function was actually called… onResponse, or onErrorResponse, neither calls the other.

kotlin.KotlinNullPointerException: 	at$continueFederated$1.onResponse(
  at <OR>$continueFederated$1.onResponse (
  at <OR>$continueFederated$1.onErrorResponse (
  at$continueFederated$1.onResponse (
  at <OR>$continueFederated$1.onResponse (
  at <OR>$continueFederated$1.onErrorResponse (
  at$MockAsyncTask.doInBackground (
  at <OR>$MockAsyncTask.onPostExecute (
  at$MockAsyncTask.onPostExecute (
  at android.os.AsyncTask.finish (
  at android.os.AsyncTask.-wrap1 (
  at android.os.AsyncTask$InternalHandler.handleMessage (
  at android.os.Handler.dispatchMessage (
  at android.os.Looper.loop (
  at (
  at java.lang.reflect.Method.invoke (
  at$ (
  at (

This is a consequence of [Stacktrace points to line after end of file?], It should be possible to map it back, but I’m not sure how to go about it. I’m not sure that there is a standalone way to reverse the stacktrace.