Update README.md

Author: gaearon

README.md

@@ -18,6 +18,7 @@ Performant and flexible.
 - [API](#api)
   - [`<Provider store>`](#provider-store)
   - [`connect([mapStateToProps], [mapDispatchToProps], [mergeProps])`](#connectmapstatetoprops-mapdispatchtoprops-mergeprops)
+- [Troubleshooting](#troubleshooting)
 - [License](#license)
 
 ## React Native
@@ -391,6 +392,50 @@ function mergeProps(stateProps, dispatchProps, parentProps) {
 export default connect(mapStateToProps, actionCreators, mergeProps)(TodoApp);
 ```
 
+## Troubleshooting
+
+Make sure to check out [Troubleshooting Redux](http://gaearon.github.io/redux/docs/Troubleshooting.html) first.
+
+### My views aren’t updating!
+
+See the link above.
+In short, 
+
+* Reducers should never mutate state, they must return new objects, or React Redux won’t see the updates.
+* Make sure you either bind action creators with `mapDispatchToState` argument to `connect()` or with `bindActionCreators()` method, or that you manually call `dispatch()`. Just calling your `MyActionCreators.addTodo()` function won’t work because it just *returns* an action, but not *dispatches* it.
+
+### My views aren’t updating on route change with React Router 0.13
+
+If you’re using React Router 0.13, you might [bump into this problem](https://github.com/gaearon/react-redux/issues/43). The solution is simple: whenever you use `<RouteHandler>` or the `Handler` provided by `Router.run`, pass the router state to it.
+
+Root view:
+
+```js
+Router.run(routes, Router.HistoryLocation, (Handler, routerState) => { // note "routerState" here
+  React.render(
+    <Provider store={store}>
+      {() => <Handler routerState={routerState} />} // note "routerState" here
+    </Provider>, document.getElementById('root'));
+});
+```
+
+Nested view:
+
+```js
+render() {
+  // Keep passing it down
+  return <RouteHandler routerState={this.props.routerState} />;
+}
+```
+
+Conveniently, this gives your components access to the router state!
+You can also upgrade to React Router 1.0 which shouldn’t have this problem. (Let us know if it does!)
+
+### I have some weird context error
+
+If you have context issues, [make sure you don’t have duplicate React](https://medium.com/@dan_abramov/two-weird-tricks-that-fix-react-7cf9bbdef375) on the page.
+Also make sure you didn’t forget to wrap your root component in [`<Provider>`](#provider-store).
+
 ## License
 
 MIT