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
Link native and WebView replays that share a trace #130595
With native-to-WebView trace linking, telemetry from a mobile app's native layer and the JavaScript SDK inside its WebViews (errors, traces, logs, metrics) is connected through a shared trace_id. Session replays from the two layers stay separate, though: one native replay and one web replay, with no way to get from one to the other in the UI.
Native mobile replays mask WebView contents by default. Developers can unmask them, but the web SDK's replay is still the most detailed view of what happened inside the WebView.
Contexts (user, OS, browser, device) stay per-layer by design. Only the trace ties the two layers together, so it's the natural place to find the related replay.
Today, to go from a native replay to the matching web replay (or back), you have to manually look up the shared trace.
Proposal: stitch native and web replays into a single playback. If that's too tricky, show links between replays that share a trace_id so you can jump between the native and web replay either way.
Activity
linear-code commentedon Nov 10, 2026
ENG-9016