samples/react-native/tm/ already ships a working TurboModule sample (NativeSampleModule, NativePlatformSampleModule). Use it as the canonical fixture for verifying the whole stack works end to end.
Tasks
- Add a screen in
samples/react-native/src/Screens/ that:
- Calls
NativeSampleModule.add(...) synchronously and NativePlatformSampleModule.getPlatform() asynchronously, with a "throw from native" button to validate Issue 2's crash context.
- Shows the resulting span attributes on screen (or logs them) so QA can eyeball without leaving the device.
- Add a Maestro flow under
samples/react-native/.maestro/ exercising the screen, gated under the ready-to-merge label like the rest of the e2e jobs (e2e-v2.yml).
- Add a small benchmark in
performance-tests/TestAppSentry/ measuring TurboModule call latency with and without enableTurboModuleTracking, surfaced in CI output.
samples/react-native/tm/already ships a working TurboModule sample (NativeSampleModule,NativePlatformSampleModule). Use it as the canonical fixture for verifying the whole stack works end to end.Tasks
samples/react-native/src/Screens/that:NativeSampleModule.add(...)synchronously andNativePlatformSampleModule.getPlatform()asynchronously, with a "throw from native" button to validate Issue 2's crash context.samples/react-native/.maestro/exercising the screen, gated under theready-to-mergelabel like the rest of the e2e jobs (e2e-v2.yml).performance-tests/TestAppSentry/measuring TurboModule call latency with and withoutenableTurboModuleTracking, surfaced in CI output.