Some folks like to have their navigation state stored in the same place as the rest of their application state. Using Redux to store your state enables you to write custom actions that manipulate the navigation state directly, to be able to dispatch navigation actions from anywhere (sometimes in a "thunk" or "saga") and to persist the navigation state in the same way you would other Redux state (your mileage may vary on this). You can read more about other use cases in the replies to this tweet.
You probably do not need to do this! Storing your React Navigation state in your own Redux store is likely to give you a very difficult time if you don't know what you're doing. You lose out on some performance optimizations that React Navigation can do for you, for example. Please do not integrate your state into Redux without first ensuring that you can do what you need to do without it!
To handle your app's navigation state in Redux, you can pass your own
navigationprop to a navigator.
statewill be fed from the reducer assigned to handle navigation state and the
dispatchwill be Redux's default
dispatch. Thus you will be able to dispatch normal redux actions using
this.props.navigation.dispatch(ACTION), reducer will update the navigation state on the basis of dispatched action, the new navigation state will then be passed to the navigator.
A middleware is needed so that any events that mutate the navigation state properly trigger the event listeners.
First, you need to add the
react-navigation-redux-helpers package to your project.
With Redux, your app's state is defined by a reducer. Each navigation router effectively has a reducer, called
getStateForAction. The following is a minimal example of how you might use navigators within a Redux application:
Once you do this, your navigation state is stored within your Redux store, at which point you can fire navigation actions using your Redux dispatch function.
Keep in mind that when a navigator is given a
navigation prop, it relinquishes control of its internal state. That means you are now responsible for persisting its state, handling any deep linking, Handling the Hardware Back Button in Android, etc.
Navigation state is automatically passed down from one navigator to another when you nest them. Note that in order for a child navigator to receive the state from a parent navigator, it should be defined as a
Applying this to the example above, you could instead define
AppNavigator to contain a nested
TabNavigator as follows:
In this case, once you
AppNavigator to Redux as is done in
MyTabNavigator will automatically have access to navigation state as a
There's a working example app with Redux here if you want to try it out yourself.
To make jest tests work with your react-navigation app, you need to change the jest preset in the
package.json, see here:
Handling the Hardware Back Button in Android
By using the following snippet, your nav component will be aware of the back button press actions and will correctly interact with your stack. This is really useful on Android.