Summary
We are seeing a low-volume native Android crash from Sentry Mobile Replay in a React Native app. The closest match I found is the closed Android SDK issue:
There is also a related closed React Native issue:
I'm opening this new React Native issue rather than only commenting on the closed Android SDK issue, so the React Native maintainers can confirm whether this is expected to be fixed by a newer RN SDK release or if there is any current recommended mitigation.
SDK / configuration
@sentry/react-native: 7.2.0 at the time of the observed events- Platform: Android
- Sentry Mobile Replay enabled
replaysSessionSampleRate: 0.1replaysOnErrorSampleRate: 1.0
Observed impact
- 3 total occurrences
- 2 unique affected users/devices
- First seen: 2026-02-10 02:14 UTC
- Last seen: 2026-05-16 22:35 UTC
- This is currently low volume, so we are not shipping an app-level workaround unless volume increases.
Affected devices/releases in retained events
- Samsung
SM-F966U, app release ending 1.1.94+158
- Samsung
SM-S938U, app release ending 1.2.00+164
Crash path
SkColorInfo::operator=
Bitmap_recycle
android.graphics.Bitmap.recycle
io.sentry.android.replay.ScreenshotRecorder.close
This looks consistent with the bitmap cleanup / screenshot recorder crash path from getsentry/sentry-java#4228.
Workaround considered
We evaluated upgrading within the v7 RN SDK line and setting Android replay to use:
Sentry.mobileReplayIntegration({
screenshotStrategy: "canvas",
})That workaround was not shipped because the crash volume is currently very low. We archived/ignored the internal Sentry issue until it escalates so we can revisit only if the event rate increases.
Question
For @sentry/react-native users who still see this ScreenshotRecorder.close / SkColorInfo::operator= path on Android, is upgrading to a newer React Native SDK version expected to include the relevant Android SDK fix from getsentry/sentry-java#4228? If so, what minimum @sentry/react-native version would you recommend?
No PII, auth headers, user identifiers, breadcrumbs, or full event payloads are included here.
Summary
We are seeing a low-volume native Android crash from Sentry Mobile Replay in a React Native app. The closest match I found is the closed Android SDK issue:
There is also a related closed React Native issue:
I'm opening this new React Native issue rather than only commenting on the closed Android SDK issue, so the React Native maintainers can confirm whether this is expected to be fixed by a newer RN SDK release or if there is any current recommended mitigation.
SDK / configuration
@sentry/react-native:7.2.0at the time of the observed eventsreplaysSessionSampleRate:0.1replaysOnErrorSampleRate:1.0Observed impact
Affected devices/releases in retained events
SM-F966U, app release ending1.1.94+158SM-S938U, app release ending1.2.00+164Crash path
This looks consistent with the bitmap cleanup / screenshot recorder crash path from getsentry/sentry-java#4228.
Workaround considered
We evaluated upgrading within the v7 RN SDK line and setting Android replay to use:
That workaround was not shipped because the crash volume is currently very low. We archived/ignored the internal Sentry issue until it escalates so we can revisit only if the event rate increases.
Question
For
@sentry/react-nativeusers who still see thisScreenshotRecorder.close/SkColorInfo::operator=path on Android, is upgrading to a newer React Native SDK version expected to include the relevant Android SDK fix from getsentry/sentry-java#4228? If so, what minimum@sentry/react-nativeversion would you recommend?No PII, auth headers, user identifiers, breadcrumbs, or full event payloads are included here.