Once we bridge native device-state breadcrumbs to JS, we'll likely hit duplicates — the same pattern we already handle for http and navigation breadcrumbs in the replay converters.
Known overlap:
- Background/foreground transitions are already captured JS-side via
AppState listener — bridging native lifecycle breadcrumbs would duplicate them
- Network breadcrumbs: JS captures XHR/fetch, native captures reachability changes — these are different signals but could be confused
Approach:
- Identify which categories overlap between JS and native
- Add filtering in the replay converters (same pattern as existing
http/navigation filters in RNSentryReplayBreadcrumbConverter)
- Or deduplicate on the JS side when receiving bridged breadcrumbs
Scope: Both native converters + JS integration. Depends on the bridging task.
Once we bridge native device-state breadcrumbs to JS, we'll likely hit duplicates — the same pattern we already handle for
httpandnavigationbreadcrumbs in the replay converters.Known overlap:
AppStatelistener — bridging native lifecycle breadcrumbs would duplicate themApproach:
http/navigationfilters inRNSentryReplayBreadcrumbConverter)Scope: Both native converters + JS integration. Depends on the bridging task.