docs(react-native): Document Session Replay network details options#18423
Open
alwx wants to merge 2 commits into
Open
docs(react-native): Document Session Replay network details options#18423alwx wants to merge 2 commits into
alwx wants to merge 2 commits into
Conversation
Add a Network Details section to the React Native Session Replay docs, covering the new `networkDetailAllowUrls`, `networkDetailDenyUrls`, `networkCaptureBodies`, `networkRequestHeaders` and `networkResponseHeaders` options on `mobileReplayIntegration`. Mirrors the structure of the existing Apple and Android Session Replay configuration pages (allow/deny list, defaults, header opt-in, body capture opt-in, 150 KB cap, server-side scrubbing note) and calls out the React Native-specific constraints \u2014 XHR-only support for now (covers axios), authorization-like headers always stripped,\n`UNPARSEABLE_BODY_TYPE` for binary bodies. Related: getsentry/sentry-react-native#6288
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
10 tasks
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
antonis
approved these changes
Jun 16, 2026
antonis
left a comment
antonis
left a comment
Contributor
There was a problem hiding this comment.
LGTM! Let's merge after shipping getsentry/sentry-react-native#6288 🎸
The React Native Session Replay SDK emits `UNPARSEABLE_BODY_TYPE` as a warning identifier, which gets referenced verbatim in the new network details docs on this branch. The typos linter (v1.47.2) flags `UNPARSEABLE` and prefers `UNPARSABLE`, but the constant name is fixed by the SDK and the docs must match. Allowlist the constant and its `UNPARSEABLE` substring in `_typos.toml`, mirroring the existing `MIGRATED_GETTING_STARTD_DOCS`/`STARTD` pattern that handles the same situation for an external Sentry backend constant. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
coolguyzone
approved these changes
Jun 16, 2026
coolguyzone
left a comment
coolguyzone
left a comment
Contributor
There was a problem hiding this comment.
LGTM! Added a commit with a hotfix that should resolve the spellchecker bug that's blocking your merge 🤙
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
3 participants
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.
DESCRIBE YOUR PR
Add a Network Details section to the React Native Session Replay docs, covering the new options on
mobileReplayIntegrationintroduced in getsentry/sentry-react-native#6288:networkDetailAllowUrlsnetworkDetailDenyUrlsnetworkCaptureBodiesnetworkRequestHeadersnetworkResponseHeadersAvailable in React Native SDK 8.15.0 and laterwhich is what's gonna be released next.IS YOUR CHANGE URGENT?
PRE-MERGE CHECKLIST
LEGAL BOILERPLATE
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
EXTRA RESOURCES