feat(android): expose tombstone options via SentryOptions.Native #5226
1 issue
code-review: Found 1 issue (1 high)
High
ReportHistoricalTombstones is mapped to the unrelated Java ReportHistoricalAnrs option - `src/Sentry/Platforms/Android/SentrySdk.cs:160`
The new .NET option ReportHistoricalTombstones is mapped to the Java SDK property ReportHistoricalAnrs. Historical ANRs and historical tombstones are distinct concepts in the Android SDK (ANRs are past Application-Not-Responding events; tombstones are native crash records from ApplicationExitInfo). Users who set ReportHistoricalTombstones=false to suppress historical tombstone reporting will instead toggle historical ANR reporting, and historical tombstone behavior will remain at the Java SDK default. This is a silent behavioral mismatch with confusing semantics that will be hard to discover.
⏱ 53.4s · 327.5k in / 2.9k out · $1.58 (+verification: $1.04)
Annotations
Check failure on line 160 in src/Sentry/Platforms/Android/SentrySdk.cs
sentry-warden / warden: code-review
ReportHistoricalTombstones is mapped to the unrelated Java ReportHistoricalAnrs option
The new .NET option `ReportHistoricalTombstones` is mapped to the Java SDK property `ReportHistoricalAnrs`. Historical ANRs and historical tombstones are distinct concepts in the Android SDK (ANRs are past Application-Not-Responding events; tombstones are native crash records from `ApplicationExitInfo`). Users who set `ReportHistoricalTombstones=false` to suppress historical tombstone reporting will instead toggle historical ANR reporting, and historical tombstone behavior will remain at the Java SDK default. This is a silent behavioral mismatch with confusing semantics that will be hard to discover.