Android Session Replay crash in ScreenshotRecorder.close / SkColorInfo::operator=

[jay-babu]

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:

• getsentry/sentry-java#4228

There is also a related closed React Native issue:

• Android crash on io.sentry.android.replay.ScreenshotRecorder.capture #5159

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.1
• replaysOnErrorSampleRate: 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.

[linear-code]

RN-631

[antonis]

Thank you for the report

The crash stack (SkColorInfo::operator= in Bitmap_recycle) is indeed the same as getsentry/sentry-java#4228 which was fixed with getsentry/sentry-java#4282 and is already included in your version (7.2.0 with sentry-android 8.21.1).

However, the same native crash stack can be triggered by a race condition in bitmap lifecycle management: ScreenshotRecorder.close() calls Bitmap.recycle() on one thread while the bitmap is still being read on another, which crashes at the same Skia code path. This race was addressed in sentry-android 8.24.0 through several fixes:

• fix(replay): Do not use recycled screenshots sentry-java#4790
• [SR] Ensure bitmaps are recycled properly sentry-java#4820
• fix(replay): Fix crash when root view has no window or is too small sentry-java#4805

There is also a remaining open edge case in the same area but that shouldn't affect your case.

@sentry/react-native 7.5.0 is the first RN SDK version that includes sentry-android 8.24.0+ (specifically 8.25.0). We recommend upgrading to the latest SDK version or 7.5.0+

Let us know if the issue persists for you and we will be happy to revisit this 🙇