Android Replays Missing & Frozen Screens

[dalnoki]

What React Native libraries do you use?

React Native without Frameworks

Are you using sentry.io or on-premise?

sentry.io (SaS)

@sentry/react-native SDK Version

6.5.0 / 6.5.9

How does your development environment look like?

Sentry.init()

https://getsentry.atlassian.net/browse/ISSUE-1724

Steps to Reproduce

Expected Result

The customer experiences issues with session replays in their React Native app on Android (iOS works fine). The issues include:

• Missing replays: Some sessions do not appear in Sentry at all, even though they were started in the mobile app.

• Frozen images in replays: For sessions that do appear, the screen image is static and does not update with navigation changes. However, timeline events (e.g., clicks/taps) are recorded correctly.

• All sessions should be recorded in Sentry Replays.

• The screen image in the replays should update dynamically with navigation changes.

Actual Result

• Some sessions do not appear in Sentry Replays.
• The replay screen remains static for all Android sessions, even though tap events are recorded.

[romtsn]

@dalnoki we'd need to get the log ouput with debug = true flag enabled from the customer. Also, is it possible that their app is a single giant webview (which we mask entirely by default with a black rectangle)?

[mykolaDokashenko]

@romtsn Our app is not a webview, just a regular react-native app. I tried to get a session for android with debug=true option, but sessions just not appear in sentry replays. E.g. we also have automation tests which are running every day couple of times, and each such run is around 70-80 tests, but in replays session I can see only 2 replays for the last 24 hours (for Android). So I`m nit sure how to provide a session witn enabled debug mode, if I could not get session replays permanently.

[romtsn]

@mykolaDokashenko thanks for your reply. Even if you don't get replays in Sentry, the log output would still be useful for us to understand what's going on (android device's logcat output, that is). Without it we can't do much to investigate the issue.