imcompatible with navigation v3

[gotexis]

Seems like navigation v3 has introduced some global app-container that must be declared explicitly so it broke the current implementation.

[spencercarli]

That's good to know. I haven't used React Navigation v3 yet. Do you have a link to an upgrade guide?

[gotexis]

Hey

Looks like there wasnt an official one, but below seems to be pretty detailed. medium

There's not a lot of breaking changes, but the main problem I found was that there need to be an explicit top-level wrapper imported from React-navigation now so whever used to be RootStack, now needs to be createAppContainer(RootStack). Seems like navigation steps are being stored into that top level container.

But then this confuses me how to set up redux. I think I've then wrapped the createAppContainer in a Store/Provider tag and it seemed to work. Only I hope that the props can propagate correctly, haven't tested.

I am a newcomer to react-native and the fact that React core functions (Redux, redux-saga, react-navigation, and even "Expo") are provided by separate groups of people is giving me aids....

[patricktargun]

Did anyone come up with a commit for this update?

[dakzh]

https://reactnavigation.org/docs/en/auth-flow.html