From 0129b7656e22616c8b7378745dcd58f84cd23c7d Mon Sep 17 00:00:00 2001 From: Roman Zavarnitsyn Date: Tue, 26 May 2026 20:58:08 +0200 Subject: [PATCH 1/2] docs(android): Add raw tombstone attachment option Document the isAttachRawTombstone option introduced in SDK 8.42.0, which sends raw tombstone data as an attachment for deeper native crash investigations. Co-Authored-By: Claude --- .../android/configuration/tombstones.mdx | 28 +++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/docs/platforms/android/configuration/tombstones.mdx b/docs/platforms/android/configuration/tombstones.mdx index 9a5751de6df23..c0f40ca662a2d 100644 --- a/docs/platforms/android/configuration/tombstones.mdx +++ b/docs/platforms/android/configuration/tombstones.mdx @@ -100,6 +100,34 @@ It can also make sense if you get recurring reports of native crashes early duri Other than that, the SDK will always pick up the latest Tombstone from the historical exit reasons list on the next app restart, and there won’t be any historical Tombstones to report. Also keep in mind that historical Tombstones will receive only minimal updates, as the available data is likely out of sync. +#### Attaching Raw Tombstone + + + +Available in Android SDK version `8.42.0` or above. + + + +The SDK can send the raw tombstone data from [ApplicationExitInfo#getTraceInputStream]() as an attachment. This is useful for performing deeper investigations using all available information from the OS, in addition to the SDK parsing the tombstone into threads with stack traces: + +```xml {filename:AndroidManifest.xml} + + + +``` + +```kotlin +SentryAndroid.init(context) { options -> + options.isAttachRawTombstone = true +} +``` + +```java +SentryAndroid.init(context, options -> { + options.setAttachRawTombstone(true); +}); +``` + #### Interaction with other Options Similar to ANR, for Tombstone derived events the options `attachThreads` and `attachStacktrace` are currently without effect. From 37e34535f9f7504b7a9ccea0e066143c6352f56e Mon Sep 17 00:00:00 2001 From: Roman Zavarnitsyn Date: Wed, 27 May 2026 10:26:24 +0200 Subject: [PATCH 2/2] docs(android): Add protobuf decoder note for raw tombstone attachment Mention that the raw tombstone data is a binary protobuf file and link to Android's tombstone schema, so users know how to interpret it. Co-Authored-By: Claude --- docs/platforms/android/configuration/tombstones.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/platforms/android/configuration/tombstones.mdx b/docs/platforms/android/configuration/tombstones.mdx index c0f40ca662a2d..ae4f55fd2f9ee 100644 --- a/docs/platforms/android/configuration/tombstones.mdx +++ b/docs/platforms/android/configuration/tombstones.mdx @@ -108,7 +108,11 @@ Available in Android SDK version `8.42.0` or above. -The SDK can send the raw tombstone data from [ApplicationExitInfo#getTraceInputStream]() as an attachment. This is useful for performing deeper investigations using all available information from the OS, in addition to the SDK parsing the tombstone into threads with stack traces: +The SDK can send the raw tombstone data from [ApplicationExitInfo#getTraceInputStream]() as an attachment. This is useful for performing deeper investigations using all available information from the OS, in addition to the SDK parsing the tombstone into threads with stack traces. + +The raw data is a binary protobuf file. To interpret it, you'll need a protobuf decoder and [Android's tombstone schema](https://android.googlesource.com/platform/system/core/+/refs/heads/main/debuggerd/proto/tombstone.proto). + +To enable raw tombstone attachments: ```xml {filename:AndroidManifest.xml}