---
title: "Discussion on \"The Stack Trace That Blamed the Wrong Screen: Making Rethrown Coroutine Exceptions Traceable on Android\" | Hashnode"
description: "Discussion on \"The Stack Trace That Blamed the Wrong Screen: Making Rethrown Coroutine Exceptions Traceable on Android\". How StackTraceRecoverable restores lost caller frames in Kotlin coroutines, and why it only works in debug, QA, and test builds."
url: "https://hashnode.com/posts/the-stack-trace-that-blamed-the-wrong-screen-making-rethrown-coroutine-exceptions-traceable-on-android/6af4a66e174b025e259a7cea"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The Stack Trace That Blamed the Wrong Screen: Making Rethrown Coroutine Exceptions Traceable on Android](https://android-expert.hashnode.dev/the-stack-trace-that-blamed-the-wrong-screen-making-rethrown-coroutine-exceptions-traceable-on-android?utm_source=hashnode&utm_medium=feed)

How StackTraceRecoverable restores lost caller frames in Kotlin coroutines, and why it only works in debug, QA, and test builds.

3d ago · 15 min read · android-expert.hashnode.dev  
Read the article

-   [#android](https://hashnode.com/tag/android)
-   [#kotlin](https://hashnode.com/tag/kotlin)
-   [#coroutines](https://hashnode.com/tag/coroutines)
-   [#kotlincoroutines](https://hashnode.com/tag/kotlincoroutines)

## Written by

[Android Expert](https://hashnode.com/@android-expert)

@android-expert · Chennai, India

  
[View profile](https://hashnode.com/@android-expert)

Android Expert· Kotlin, Jetpack Compose & production pitfalls

Android Engineer & Kotlin Advocate. 🚀 Deep dives into Jetpack Compose, Coroutines, and Clean Architecture. Turning complex code into scalable solutions. 🛠️✨

## Responses

Markdown supported · ⌘↵ to post

No responses yet.