Before writing any bridging code, we need to understand the current state. Sentry Cocoa and Android SDKs generate device-state breadcrumbs natively (memory warnings, thermal state, low-power mode, battery, network reachability). The replay converters pass unrecognized categories through via defaultConverter (iOS RNSentryReplayBreadcrumbConverter.m:50, Android RNSentryReplayBreadcrumbConverter.java:42).
Questions to answer:
- Which native breadcrumb categories actually appear in a real replay session?
- Which of those appear in
event.breadcrumbs on JS-originated error events? (Likely none — native breadcrumbs don't cross the bridge to JS)
- Are any categories missing entirely on one platform?
- What's the formatting like for the ones that do show up in replay?
Method: Run the sample app, trigger memory warnings / network changes / background-foreground, capture an error + replay, check Sentry UI.
Scope: Investigative — no code changes, just documenting findings to inform subsequent tasks.
Before writing any bridging code, we need to understand the current state. Sentry Cocoa and Android SDKs generate device-state breadcrumbs natively (memory warnings, thermal state, low-power mode, battery, network reachability). The replay converters pass unrecognized categories through via
defaultConverter(iOSRNSentryReplayBreadcrumbConverter.m:50, AndroidRNSentryReplayBreadcrumbConverter.java:42).Questions to answer:
event.breadcrumbson JS-originated error events? (Likely none — native breadcrumbs don't cross the bridge to JS)Method: Run the sample app, trigger memory warnings / network changes / background-foreground, capture an error + replay, check Sentry UI.
Scope: Investigative — no code changes, just documenting findings to inform subsequent tasks.