releases.shpreview

Fatal React Native JS errors no longer double-captured

@posthog/react-native-plugin@2.0.1

1 enhancement1 fixThis release1 enhancementImprovements to existing features1 fixBug fixesAI-tallied from the release notes

2.0.1

Patch Changes

  • #3824 bd80c7c Thanks @ioannisj! - Drop native captures of fatal React Native JS errors that the JS layer already reports, so a fatal JS error no longer produces two $exception events. Works on Android (both architectures) and iOS (old architecture only). On the iOS new architecture, fatal JS exception events surface as a generic SIGABRT crash event with no JS-error text in any field, so they currently cannot be filtered (2026-06-12)

  • #3824 bd80c7c Thanks @ioannisj! - Apply the session replay configuration at native SDK setup even when replay starts disabled, so recording turned on later (e.g. startRecording or a linked feature flag) uses screenshot mode, the configured masking, and the configured snapshot endpoint instead of wireframe/default settings (2026-06-12)

Fetched June 12, 2026