Inside Mobile Session Replay: Smarter Debugging
summary
Sentry’s mobile session replay reproduces real sessions by capturing view-hierarchy snapshots and screenshots at 1 frame per second, compressing them into segments while masks all text and images by default and offering selective unmasking. Performance is measured on Pocketcast with CPU and memory impact but remains imperceptible for most users. A demo shows a checkout returning HTTP 500 occurring 53 times across 34 users in release 24.12.26, traced to a backend “not enough inventory” exception; SEIR proposes a root cause and a pull request fix.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:06Debugging user-facing issues
- 1:47Session replay benefits
- 2:52Platform & implementation
- 3:33Privacy features
- 4:19Performance overhead
- 6:03Demo app overview
- 7:10Debugging with Sentry
- 8:13Replay view & context
- 9:35Breadcrumbs & device data
- 11:02Network traces in replays
- 12:25Backend tracing & AI root cause
- 13:28Tags & session filtering
- 14:10Call to action
related talks
19mSolve your Mobile Bugs with Session Replay
26mVisualizing the Unseen to Fix Errors Faster with Sentry’s Session Replay Live
12mSolve 100% of your errors
09mSession Replay
26mIt Worked on My iPhone 15 Pro Max…
14mTracing: Frontend Issues With Backend Solutions
08mMonitoring Errors and Slowdowns Across JS Applications
26mLogging, and Errors, and Metrics Oh My!