Skip to content

feat(android): expose tombstone options via SentryOptions.Native #5226

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jamescrosswell wants to merge 3 commits into
base: main
Choose a base branch
from

feat(android): expose tombstone options on Native options

07eee64
Select commit
Loading
Failed to load commit list.
Open

feat(android): expose tombstone options via SentryOptions.Native #5226

feat(android): expose tombstone options on Native options
07eee64
Select commit
Loading
Failed to load commit list.
@sentry/warden / warden: find-bugs completed May 12, 2026 in 2m 8s

1 issue

find-bugs: Found 1 issue (1 high)

High

ReportHistoricalTombstones is incorrectly mapped to ReportHistoricalAnrs - `src/Sentry/Platforms/Android/SentrySdk.cs:160`

The new managed option options.Native.ReportHistoricalTombstones is assigned to the Java SDK's o.ReportHistoricalAnrs field. ANRs (Application Not Responding) and tombstones are distinct Android crash-reporting concepts in the Sentry Java SDK. As a result, toggling ReportHistoricalTombstones will silently change historical ANR reporting behavior instead of (or in addition to) historical tombstone behavior, and any actual historical-tombstone Java option remains unconfigured. This also conflicts with the documentation on NativeOptions.ReportHistoricalTombstones which states it controls historical tombstones.

⏱ 55.1s · 263.5k in / 2.7k out · $0.88 (+verification: $0.54)

Annotations

Check failure on line 160 in src/Sentry/Platforms/Android/SentrySdk.cs

See this annotation in the file changed.

@sentry-warden sentry-warden / warden: find-bugs

ReportHistoricalTombstones is incorrectly mapped to ReportHistoricalAnrs 

The new managed option `options.Native.ReportHistoricalTombstones` is assigned to the Java SDK's `o.ReportHistoricalAnrs` field. ANRs (Application Not Responding) and tombstones are distinct Android crash-reporting concepts in the Sentry Java SDK. As a result, toggling `ReportHistoricalTombstones` will silently change historical ANR reporting behavior instead of (or in addition to) historical tombstone behavior, and any actual historical-tombstone Java option remains unconfigured. This also conflicts with the documentation on `NativeOptions.ReportHistoricalTombstones` which states it controls historical tombstones.
View more details on @sentry/warden