The latest version of React Navigation now has a new unstable API to automatically navigate to the correct screen after a conditional render (e.g., if a screen was opened via a deep link, but was behind auth) Just pass `UNSTABLE_routeNamesChangeBehavior="lastUnhandled"`

need this 😄

huge!

Documentation is available here

Nice! Are we getting this with expo router too? @expo @Baconbrix

Is there a specific version this is available on? I'm getting a typescript error on the latest native-stack

Make sure to also update @react-navigation/native

interesting

@Baconbrix expo-router?

can you use this with 0.79?

Yes

Looking great! Although It would be really helpful if the team could also look into the outstanding performance issues when upgrading to React Navigation 7.x with the new React Native arch. Without it adoption of this fine new features are unlikely.

There is no repro, comparison video, or any information to know what exactly is slow. Without such info, how do we verify where the bug is or whether any changes will actually fix your issue?

I am not the author of the issue, but I do face it. In this specific case given the number of people affected and also the straightforward nature of reproduction: comparing prod 6.x to 7.x with new arch. enabled people might think it is redundant. I can create new issue with repr

We always ask for repro and tell you why. Repro, videos, etc., minimize miscommunication and help pinpoint what to debug and where the issue is. If it's straightforward to repro, it should be easy to provide a repro as well.

In the end, maintainers have many other things to do. If you don't make it easy for the maintainers to look at an issue you have, it's simply not going to be prioritized. People should also help out with the work in Open Source projects. Providing a clear repro is part of it.