Native SDKs (Cocoa/Android) generate breadcrumbs for memory warnings, thermal state, low-power mode, battery level, and network reachability — but these stay in the native breadcrumb store. They may appear in replay (via defaultConverter passthrough) but they don't appear in event.breadcrumbs on JS-originated events, beforeBreadcrumb callbacks, or the breadcrumb list on the issue detail page.
We should bridge relevant native device-state breadcrumbs to the JS side so they're available everywhere, not just replay.
Considerations:
- Performance: don't flood the bridge on every breadcrumb — batch or filter to useful categories only
- Decide which categories are worth bridging (memory warnings and network changes are high value; battery level on every tick is not)
- Bridge mechanism: callback from native module, or periodic sync?
Scope: Native module changes in RNSentry.m / RNSentryModule.java + JS-side breadcrumb integration. Depends on findings from the audit task.
Native SDKs (Cocoa/Android) generate breadcrumbs for memory warnings, thermal state, low-power mode, battery level, and network reachability — but these stay in the native breadcrumb store. They may appear in replay (via
defaultConverterpassthrough) but they don't appear inevent.breadcrumbson JS-originated events,beforeBreadcrumbcallbacks, or the breadcrumb list on the issue detail page.We should bridge relevant native device-state breadcrumbs to the JS side so they're available everywhere, not just replay.
Considerations:
Scope: Native module changes in
RNSentry.m/RNSentryModule.java+ JS-side breadcrumb integration. Depends on findings from the audit task.