Sentry Android SDK Now Reads Native Crash Tombstones
On Android 12+, Sentry now reads the platform's tombstone output, delivering fuller, lighter and easier-to-analyze native crash reports for app teams.
Android's built-in crash recorder, debuggerd, captures the crashing thread, every other running thread, register state and memory maps into files called tombstones. For years these weren't readable programmatically from inside an app, forcing crash-reporting SDKs like Sentry's to maintain their own native infrastructure via a fork of libunwindstack patched to build with the NDK — adding roughly 1MiB of binary weight per ABI, missing Java/Kotlin frame symbolication, and capturing only the crashing thread's context.
ApplicationExitInfo in Android 11 and the native crash trace stream added in Android 12 changed that. Starting with version 8.30.0, Sentry's Android SDK reads this stream directly on Android 12+ devices and ships tombstone data as a native crash event. The result: fully symbolicated stack traces for every thread, resolved Java/Kotlin frames, zero extra binary overhead, and maintenance responsibility shifted from Sentry's fork to the platform itself.
The change meaningfully simplifies debugging for native Android apps. With roughly 69% of over 2 billion Android error events ingested in the past 30 days coming from Android 12+ devices, the improvement benefits the vast majority of current users. Existing Native SDK/NDK integrations remain compatible and can run alongside tombstone support without conflicts.