Repository navigation
Conversation
…w traces Add a "Connect Traces" section to the React Native WebView page covering the new `sentryWebViewProps` helper (available in SDK 8.29.0): usage, `allowedHosts` gating, the Android `onMessage` requirement, entry-pageload scope, and cross-project trace stitching. Remove the outdated statement that the SDK doesn't interact with web views. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
| File | Line | Current Link | Should Be |
|---|---|---|---|
docs/platforms/react-native/common/configuration/webview.mdx |
44 | /platforms/javascript |
/platforms/javascript/ |
Each redirect hop loses ~15% of SEO link equity and adds latency for users.
- Bump the `sentryWebViewProps` availability note to 8.32.0. - Note that the root span name (`sentry-transaction`) is stripped from `baggage` before injection. - Document composing your own `injectedJavaScriptBeforeContentLoaded` by concatenation instead of overriding it. - Add security guidance: an allow-listed page running untrusted JS can feed misleading/polluted data into the connected trace; don't allow-list pages that render untrusted content. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The change adds a Connect Traces section to an existing WebView guide. The plan checks page loads on that guide, inherited Expo copies of it, client errors, and MDX not-found logs. An issue escalates when those pages stop loading or when client errors or MDX not-found logs appear. Services: Mention PlanWhat changedReaders of the React Native WebView page now see a Connect Traces section. That section documents spreading sentryWebViewProps onto WebView to continue a native trace. The Expo WebView page inherits this MDX and serves the same section. A production deploy of sentry-docs must finish before the copy is live. Vercel project sentry-docs ships this file. The applicationKey tag sentry-docs matches that catalog id. develop-docs does not ship RiskBroken MDX can 404 both WebView pages or fail the static build. New code samples can throw in the code-tab client on those pages. Sibling React Native configuration pages share the same renderer and platform tree. Intended effectThis is a documentation edit. Connected telemetry cannot show that the new section is in the served HTML. Do not treat page load volume as proof the new copy is live. Absent has no queryable form for this change. Regression watchA render or compile fault on this MDX can 404 the React Native WebView page and the inherited Expo page. Watch client errors first. Then watch MDX not-found logs. Then watch page loads on those two URLs against sibling configuration volume. Traces are sampled at 30 percent. These URLs had no pageload spans in the baseline window. Use the page load counter, not span duration.
Not observableThe served HTML does not expose whether Connect Traces or sentryWebViewProps is present. Pageload p95 is not usable. The 30 percent trace sample returned 0 spans for these URLs in 2026-10-14T14:49:49Z to 2026-10-16T14:49:49Z. |




DESCRIBE YOUR PR
Documents the new
sentryWebViewPropshelper (React Native SDK 8.32.0) for connecting React Native traces with embedded WebViews.Updates
docs/platforms/react-native/common/configuration/webview.mdx:<WebView>usage,allowedHostsgating (host + subdomain, case-insensitive), the requirement that the web page run a Browser SDK withbrowserTracingIntegration, the AndroidonMessagerequirement + spread order, entry-pageload scope, and cross-project (same-org) trace stitching.Corresponding SDK PR: getsentry/sentry-react-native#6794
IS YOUR CHANGE URGENT?
PRE-MERGE CHECKLIST
EXTRA RESOURCES
🤖 Generated with Claude Code