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):

UNSTABLE_routeNamesChangeBehavior="lastUnhandled"

reactnavigation.org/docs/auth-fl...

It was broken for a while because the format of the stack traces had changed since the initial implementation.

This is how it looked when it was broken. Not very useful.

Do you use React Navigation devtools?

It should now display the stack trace correctly. So you can easily see where the navigation originated from.