Warning: in the next major version of React Navigation, to be released in Fall 2018, we will no longer provide any information about how to integrate with Redux and it may cease to work. Issues related to Redux that are posted on the React Navigation issue tracker will be immediately closed. Redux integration may continue to work but it will not be tested against or considered when making any design decisions for the library.
Some folks like to have their navigation state stored in the same place as the rest of their application state. Think twice before you consider doing this, there is an incredibly good chance that you 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.
If your only reason for doing this is that you want to be able to perform navigation actions from outside of your components (eg: from a Redux middleware), you can learn more about this in navigating without the navigation prop.
To handle your app's navigation state in Redux, you can pass your own
navigationprop to a navigator.
react-navigation-redux-helpershandles this for you behind the scenes with a "higher-order component" called
reduxifyNavigator. You pass in your root navigator component to the
reduxifyNavigatorfunction, and it returns a new component that takes your navigation
dispatchfunction as props.
A middleware is needed so that any events that mutate the navigation state properly trigger React Navigation's event listeners.
The navigation state inside Redux will need to be kept updated using React Navigation's navigation reducer. You will call this reducer from your Redux master reducer.
First, you need to add the
react-navigation-redux-helpers package to your project.
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:
Under the hood
Creating your own navigation reducer
If you want to replace
createNavigationReducer reducer creator this is how you would do it yourself:
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.