[skill-drift] fix(sentry-react-native-sdk): document network body capture in Session Replay#210
Merged
antonis merged 1 commit intoJun 23, 2026
Conversation
…ture in Session Replay Automated drift-fix run. Co-Authored-By: Claude (claude-sonnet-4-5) <noreply@anthropic.com>
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
| | **Touch recording** | Full pointer/mouse events | Tap breadcrumbs only (no gesture paths) | | ||
| | **Rage clicks** | ✅ Detected | ❌ Not supported | | ||
| | **Network bodies** | ✅ Optional capture | ❌ Not captured | | ||
| | **Network bodies** | ✅ Optional capture | ✅ **Opt-in capture** (XHR only, SDK ≥8.13.0) | |
There was a problem hiding this comment.
Bug: The documentation contains a contradiction. The "Known Limitations" table at line 528 incorrectly states network body capture is unavailable, contradicting updates elsewhere in the file.
Severity: LOW
Suggested Fix
Update the "Known Limitations vs. Web Replay" table in skills/sentry-react-native-sdk/references/session-replay.md at line 528. Change the entry for "Network request bodies" on mobile from "❌ Not available" to reflect that it is now available as an opt-in feature, consistent with the information on line 24.
Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.
Location: skills/sentry-react-native-sdk/references/session-replay.md#L24
Potential issue: The documentation for Session Replay in `session-replay.md` contains
contradictory information about the availability of network body capture on mobile.
While the feature comparison table on line 24 was updated to show "Opt-in capture", the
"Known Limitations vs. Web Replay" table on line 528 was not updated and still
incorrectly states the feature is "Not available". This inconsistency can cause
confusion for users and AI models trying to understand the SDK's capabilities, as
different sections of the same document provide conflicting details about the same
feature.
Also affects:
skills/sentry-react-native-sdk/references/session-replay.md:329~389
Did we get this right? 👍 / 👎 to inform future reviews.
antonis
deleted the
skill-drift/sentry-react-native-sdk-skill-drift-fix-sentry-react-native-sdk--1782139066
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Warning
Auto-generated from external SDK content. Review all links and code suggestions before acting on them.
Summary
Documents the new opt-in network request/response body capture feature for Session Replay, introduced in PR #6288 (merged 2026-06-16).
Changes
Updated comparison table (line 24): Changed "Network bodies: ❌ Not captured" → "✅ Opt-in capture (XHR only, SDK ≥8.13.0)"
Rewrote "Network Request Capture" section (lines 325-336):
fetchcoming in future release)Added 5 new options to
mobileReplayIntegration()table (lines 141-146):networkDetailAllowUrls— URLs to enrich with headers/bodiesnetworkDetailDenyUrls— URLs to never enrichnetworkCaptureBodies— Opt in to body capture (default: false)networkRequestHeaders— Extra request headers to capturenetworkResponseHeaders— Extra response headers to captureUpstream PR
Scope
Feature is opt-in (empty default allow list +
networkCaptureBodies: falseby default) and covers XHR requests only (includesaxios; nativefetchsupport planned for future release).Source PRs