You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Record network request/response bodies in Session Replay #4106
@krystofwoldrich any update on when we can expect this? Inspecting network request/response bodies is pretty vital for debugging issues in production 🤞🏽
@george-g-y-b thanks for your interest - we are currently focusing on other improvements to SR, but given the interest in this feature, we prioritize it among the first new functionalities we're going to add. Please follow the updates in this GH issue.
Reacted by jackstudd, Antonis Lilis, Noah Otinkorang Boye and Hassan Al Rawi
Activity
jackstudd commentedon Sep 25, 2024
Looks like web have it, I don't get why RN doesn't => getsentry/sentry-javascript#7103
[-][Session Replay] - Record network[/-][+][Session Replay] - Record network request body[/+]krystofwoldrich commentedon Oct 2, 2024
Thank you for the message @jackstudd.
This is correct, currently the RN Replay Implementation does not record the request and response body.
I'll mark this as a feature requests and we will post updates here.
[-][Session Replay] - Record network request body[/-][+]Record network request/response bodies in Session Replay[/+]shmkane commentedon Feb 18, 2025
Just curious how the Sentry team prioritizes GH issues -- Is this on y'alls radar as a to-do item, or waiting for more thumbs ups/community feedback?
10 remaining items
george-g-y-b commentedon Aug 13, 2025
@krystofwoldrich any update on when we can expect this? Inspecting network request/response bodies is pretty vital for debugging issues in production 🤞🏽
kahest commentedon Aug 18, 2025
@george-g-y-b thanks for your interest - we are currently focusing on other improvements to SR, but given the interest in this feature, we prioritize it among the first new functionalities we're going to add. Please follow the updates in this GH issue.
github-actions commentedon Jun 18, 2026
A PR closing this issue has just been released 🚀
This issue was referenced by PR #6288, which was included in the 8.15.0 release.