The test at lines 51–55 passes a { push: jest.fn() } router and asserts the router is "unchanged", but the new code now mutates router.push with a wrapped function and sets __sentryWrapped. The toBe (reference equality) assertion still passes, so the test silently no longer verifies its stated intent and could mask future regressions in navigation-method wrapping.

The prefetch signature now references ExpoRouterHref (a non-exported type) in the public ExpoRouter interface. TypeScript consumers who need to explicitly reference this parameter type can no longer do so — they'd have to use a workaround like Parameters<NonNullable<ExpoRouter['prefetch']>>[0]. Export ExpoRouterHref from packages/core/src/js/tracing/index.ts to restore full API usability.

wrapExpoRouter sets pendingExpoRouterNavigation before invoking the original router method and only clears it on the throw path. On the success path it relies on startIdleNavigationSpan (registered as the __unsafe_action__ listener on the navigation container) to call consumePendingExpoRouterNavigation(). If the wrapped call succeeds but the listener never fires for it — for example because registerNavigationContainer has not been called yet, or the underlying router call is intercepted before reaching React Navigation's dispatch — the module-level pending value persists and will be consumed (and incorrectly attributed) by the next unrelated navigation. Adding a finally-style clear (or ensuring drain after original.apply) would make the contract symmetric with the catch branch.