[alwx]

📢 Type of change

• Bugfix

📜 Description

expoRouterIntegration now gets the navigation container ref from the public useNavigationContainerRef export. It computes route info with getRouteInfoFromState, which Expo Router 57 and 58 both have at the same path. On Expo Router 58, the integration listens to the internal actionDispatched event and starts navigation spans through a new internal _startIdleNavigationSpan method on reactNavigationIntegration.

💡 Motivation and Context

Expo Router 58 removed expo-router/build/global-state/router-store and stopped sending __unsafe_action__. Metro then warned on every bundle, and the integration could not start navigation spans. Fixes #6901.

💚 How did you test it?

I ran expo export on samples/expo (expo-router 58.0.23). The warning appeared 10 times before this change and 0 times after it. I added unit tests for the new route info source, the action listener, and the listener cleanup.

📝 Checklist

• I added tests to verify changes.
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
• No breaking changes.

🔮 Next steps

On Expo Router 58, actionDispatched fires after the new screen renders, so spans start a bit late. A follow-up can use the expo-router:action-enqueued performance mark for an earlier start time.

[github-actions]

Semver Impact of This PR

⚪ None (no version bump detected)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

• fix(tracing): Support Expo Router 58 in expoRouterIntegration by alwx in #6923

• chore(deps): update Wizard to v9.0.0 by github-actions in #6936
• chore(deps): update CLI to v3.8.2 by github-actions in #6933
• ci: Move CI off end-of-life Node versions to Node 22 by antonis in #6927

---

_{🤖 This preview updates automatically when you update the PR.}

[github-actions]

	Fails
🚫	Pull request is not ready for merge, please add the "ready-to-merge" label to the pull request

Generated by 🚫 dangerJS against 1246c96

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit fc6a0b5. Configure here.}

[antonis]

Thanks for tackling this! The Expo Router 58 path looks right: actionDispatched fires before the container's state event, and v57 has no internalNavigationEvents, so no navigation gets two spans.

Two blockers for older versions, details inline:

1. Expo Router ≤55 silently loses the integration (getRouteInfoFromState is missing).
2. v56/57 regress #6431 (navigationRef is read only once).

I verified both against the published expo-router packages (4.x through 58.x).

[invivek26]

We backported this PR (at 1246c96) onto 8.28.0 to run expo-router 58.0.25, and real route changes now get navigation spans with the templated route name. Thanks for this.

One thing we hit on 58: actionDispatched fires for every reducer action, not only navigations. On a cold launch with tabs we saw ROUTE_NAMES_CHANGED twice and PRELOAD once per tab. router.prefetch() gives more PRELOADs and another ROUTE_NAMES_CHANGED, and param updates send SET_PARAMS.

expoRouterIntegration leaves useDispatchedActionData off, so startIdleNavigationSpan doesn't filter any of these. Each one starts an idle span, and the next state event keeps the same route key. The span then ships on its idle timeout as an unnamed Route Change navigation transaction with no route data. We got one on every cold launch and one per router.prefetch().

We worked around it by forwarding only navigation actions from the listener:

const NAVIGATION_ACTION_TYPES = new Set([
    'NAVIGATE',
    'NAVIGATE_TO_HREF',
    'PUSH',
    'REPLACE',
    'GO_BACK',
    'POP',
    'POP_TO',
    'POP_TO_TOP',
    'JUMP_TO',
    'RESET',
]);

// in the actionDispatched listener, after the `!event.actionType` check
if (!NAVIGATION_ACTION_TYPES.has(event.actionType)) {
    return;
}

With that, a cold launch ships one ui.load and nothing else. Tab switches (NAVIGATE), pushes, deep links and replace each ship one templated navigation transaction. GO_BACK still starts a span, and the empty-back rule drops it as before.

A denylist (PRELOAD, SET_PARAMS, ROUTE_NAMES_CHANGED) would also work for what we saw. But router 58's reducer has other internal actions too (REMOVE_ROUTES, NAVIGATOR_CHANGED, REPORT_CONSUMED), so an allowlist seemed safer.