`handleLateDeepLink` in `reactnavigation.ts` is invoked synchronously for every deep link via the registered pendingDeepLink listener, including warm-open `url` events. It picks `latestNavigationSpan ?? lastIdleNavSpan`. After a completed navigation `latestNavigationSpan` is `undefined`, so it falls back to `lastIdleNavSpan`, which is never cleared and keeps pointing at the previous screen's idle span. If that span is still recording (within its 1s idle timeout), the listener tags the *previous* span and returns `true`, so `setPendingDeepLink` never stores the URL. The navigation actually triggered by the deep link is then created moments later and finds nothing to consume in `updateLatestNavigationSpanWithCurrentRoute`, leaving it untagged while the wrong span carries `navigation.trigger=deeplink`.

`handleLateDeepLink` in `reactnavigation.ts` is invoked synchronously for every deep link via the registered pendingDeepLink listener, including warm-open `url` events. It picks `latestNavigationSpan ?? lastIdleNavSpan`. After a completed navigation `latestNavigationSpan` is `undefined`, so it falls back to `lastIdleNavSpan`, which is never cleared and keeps pointing at the previous screen's idle span. If that span is still recording (within its 1s idle timeout), the listener tags the *previous* span and returns `true`, so `setPendingDeepLink` never stores the URL. The navigation actually triggered by the deep link is then created moments later and finds nothing to consume in `updateLatestNavigationSpanWithCurrentRoute`, leaving it untagged while the wrong span carries `navigation.trigger=deeplink`.

`handleLateDeepLink` in `reactnavigation.ts` is invoked synchronously for every deep link via the registered pendingDeepLink listener, including warm-open `url` events. It picks `latestNavigationSpan ?? lastIdleNavSpan`. After a completed navigation `latestNavigationSpan` is `undefined`, so it falls back to `lastIdleNavSpan`, which is never cleared and keeps pointing at the previous screen's idle span. If that span is still recording (within its 1s idle timeout), the listener tags the *previous* span and returns `true`, so `setPendingDeepLink` never stores the URL. The navigation actually triggered by the deep link is then created moments later and finds nothing to consume in `updateLatestNavigationSpanWithCurrentRoute`, leaving it untagged while the wrong span carries `navigation.trigger=deeplink`.

`handleLateDeepLink` in `reactnavigation.ts` is invoked synchronously for every deep link via the registered pendingDeepLink listener, including warm-open `url` events. It picks `latestNavigationSpan ?? lastIdleNavSpan`. After a completed navigation `latestNavigationSpan` is `undefined`, so it falls back to `lastIdleNavSpan`, which is never cleared and keeps pointing at the previous screen's idle span. If that span is still recording (within its 1s idle timeout), the listener tags the *previous* span and returns `true`, so `setPendingDeepLink` never stores the URL. The navigation actually triggered by the deep link is then created moments later and finds nothing to consume in `updateLatestNavigationSpanWithCurrentRoute`, leaving it untagged while the wrong span carries `navigation.trigger=deeplink`.

When `applyPendingDeepLinkToSpan` short-circuits because the span is already in `taggedDeepLinkSpans`, it returns early without calling `consumePendingDeepLink`, leaving any previously-stored pending link in the slot. A subsequent navigation's `applyPendingDeepLinkToSpan` call then consumes and applies the stale link, attributing the wrong URL to an unrelated span.

When `applyPendingDeepLinkToSpan` short-circuits because the span is already in `taggedDeepLinkSpans`, it returns early without calling `consumePendingDeepLink`, leaving any previously-stored pending link in the slot. A subsequent navigation's `applyPendingDeepLinkToSpan` call then consumes and applies the stale link, attributing the wrong URL to an unrelated span.