The Silent Killers: How to Debug Android App Exits You Never Knew Happened
Stop relying on Crashlytics alone. Learn how to use ApplicationExitInfo to track LMKs, silent ANRs, and native process kills. Every Android developer has been there: you look at your Google Play Console, and the crash rate looks “clean.” But then you check your reviews, and users are complaining that the app “just closes” or “restarts randomly.” The truth is, many app terminations happen in the shadows. Whether it’s a system-level process kill due to low memory or a user force-stopping the app, these events often bypass traditional crash reporters like Firebase Crashlytics. Thankfully, since Android 11, we have a specialized diagnostic tool: ApplicationExitInfo . Why Standard Crash Reporting Leaves You Blind Most crash SDKs rely on Thread.setDefaultUncaughtExceptionHandler . This works for JVM-level fatal exceptions, but it is effectively blind when: The OS kills your process to reclaim RAM (Low Memory Killer). The User force-closes the app from System Set...