fix(tracing): Guard getNewScreenTimeToDisplay behind enableTimeToInitialDisplay (#5849)

* fix(tracing): Guard getNewScreenTimeToDisplay behind enableTimeToInitialDisplay

NATIVE.getNewScreenTimeToDisplay() was called on every navigation state
change regardless of whether enableTimeToInitialDisplay was enabled.
This native bridge call posts to the main thread and registers a
Choreographer callback (Android) or CADisplayLink (iOS) to capture the
next frame timestamp.

On low-end devices (Fire TV, Chromecast) this is measurable overhead
that the user could not avoid even after setting
enableTimeToInitialDisplay: false.

The dispatch-time native calls (setActiveSpanId, navigationProcessingSpan)
were already correctly guarded behind the flag. This aligns the
state-change-time call with the same guard.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* docs: Add changelog entry for navigation integration performance fixes

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

* docs(tracing): Add performance note to enableTimeToInitialDisplay JSDoc

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: antonis

CHANGELOG.md

@@ -6,6 +6,13 @@
 > make sure you follow our [migration guide](https://docs.sentry.io/platforms/react-native/migration/) first.
 <!-- prettier-ignore-end -->
 
+## Unreleased
+
+### Fixes
+
+- Reduce `reactNavigationIntegration` performance overhead ([#5840](https://github.com/getsentry/sentry-react-native/pull/5840), [#5842](https://github.com/getsentry/sentry-react-native/pull/5842), [#5849](https://github.com/getsentry/sentry-react-native/pull/5849))
+- Fix duplicated breadcrumbs on Android ([#5841](https://github.com/getsentry/sentry-react-native/pull/5841))
+
 ## 8.5.0
 
 ### Features
@@ -22,7 +29,6 @@
 
 - Fix native frames measurements being dropped due to race condition ([#5813](https://github.com/getsentry/sentry-react-native/pull/5813))
 - Fix app start data lost when first navigation transaction is discarded ([#5833](https://github.com/getsentry/sentry-react-native/pull/5833))
-- Fix duplicated breadcrumbs on Android ([#5841](https://github.com/getsentry/sentry-react-native/pull/5841))
 
 ### Dependencies
 

packages/core/src/js/tracing/reactnavigation.ts

@@ -117,6 +117,9 @@ interface ReactNavigationIntegrationOptions {
    * Time to initial display measures the time it takes from
    * navigation dispatch to the render of the first frame of the new screen.
    *
+   * Note: Enabling this adds native bridge calls on every navigation
+   * which may cause noticeable overhead on low-end devices.
+   *
    * @default false
    */
   enableTimeToInitialDisplay: boolean;
@@ -438,7 +441,9 @@ export const reactNavigationIntegration = ({
       return undefined;
     }
 
-    addTimeToInitialDisplayFallback(latestNavigationSpan.spanContext().spanId, NATIVE.getNewScreenTimeToDisplay());
+    if (enableTimeToInitialDisplay) {
+      addTimeToInitialDisplayFallback(latestNavigationSpan.spanContext().spanId, NATIVE.getNewScreenTimeToDisplay());
+    }
 
     if (previousRoute?.key === route.key) {
       debug.log(`[${INTEGRATION_NAME}] Navigation state changed, but route is the same as previous.`);

packages/core/test/tracing/reactnavigation.ttid.test.tsx

@@ -585,6 +585,16 @@ describe('React Navigation - TTID', () => {
         }),
       );
     });
+
+    test('should not call getNewScreenTimeToDisplay when ttid is disabled', () => {
+      jest.runOnlyPendingTimers(); // Flush app start transaction
+
+      mockWrapper.NATIVE.getNewScreenTimeToDisplay.mockClear();
+      mockedNavigation.navigateToNewScreen();
+      jest.runOnlyPendingTimers(); // Flush navigation transaction
+
+      expect(mockWrapper.NATIVE.getNewScreenTimeToDisplay).not.toHaveBeenCalled();
+    });
   });
 
   describe('ttid for preloaded/seen routes', () => {