You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BT-011] Implement Tab Navigator Resolution for Dynamic Routes #85750
The dynamic route permission check only validates the deepest (leaf) route in a dynamic route chain
If the leaf route is not an authorized entry screen, the router returns Not Found, even though a parent route in the chain is a valid entry screen
Example: URL /debug/report/123/details/constant-picker — the router only checks ConstantPicker, which is not an allowed entry screen, and returns Not Found. But Debug is a valid entry screen, so the URL should be allowed
There is existing related logic in findFocusedRouteWithOnyxTabGuard that partially handles this but needs adaptation for dynamic routes
Expected State:
The permission check should validate the entire route chain, not just the leaf route
If any parent route in the chain is an authorized entry screen, the dynamic route should be allowed
Tab navigators should be properly resolved when building navigation state for dynamic routes
This should leverage and extend the existing findFocusedRouteWithOnyxTabGuard logic rather than modifying getPathFromState
Context:
Discovered during PR #85426 (Debug page migration)
@collectioneur identified that findFocusedRouteWithOnyxTabGuard already covers similar functionality and just needs a tweak for these cases
changed the title [-][BT-011] Implement Tab Navigator Resolution for Dynamic Routes[/-][+][Due for payment 2026-03-31] [BT-011] Implement Tab Navigator Resolution for Dynamic Routes[/+]on Mar 24, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.42-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
changed the title [-][Due for payment 2026-03-31] [BT-011] Implement Tab Navigator Resolution for Dynamic Routes[/-][+][BT-011] Implement Tab Navigator Resolution for Dynamic Routes[/+]on Mar 24, 2026
Activity
[-][BT-011] Implement Tab Navigator Resolution for Dynamic Routes[/-][+][Due for payment 2026-03-31] [BT-011] Implement Tab Navigator Resolution for Dynamic Routes[/+]melvin-bot commentedon Mar 24, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Mar 24, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.42-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-03-31. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Mar 24, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)mjasikowski commentedon Mar 24, 2026
No payment needed - fixed price project
[-][Due for payment 2026-03-31] [BT-011] Implement Tab Navigator Resolution for Dynamic Routes[/-][+][BT-011] Implement Tab Navigator Resolution for Dynamic Routes[/+]