React-redux-universal-hot-example: ReduxAsyncConnect fires in Client Side when it shouldn't

Created on 16 Mar 2016 · 8Comments · Source: erikras/react-redux-universal-hot-example

While using boilerplate i found some problem.
In reduxAsyncConnect I'm using getData() from my reducer, which loads some info from db. Later, I have a button, that changes one of returned values, but the value remain unchanged for the first time. Clicking second, third, etc. time it works perfectly correct. I think that I found where the problem is - clicking on button, which fires another function from reducer, trigggers some other actions - including "@@router/UPDATE_LOCATION", "reduxAsyncConnect/BEGIN_GLOBAL_LOAD" and "reduxAsyncConnect/END_GLOBAL_LOAD". Also it fires my action that is in reduxAsyncConnect, which causes reseting my reducer to initial state.

It can be checked even on clean boilerplate - all you need to do is to add console.log(action.type) in, for example redux/modules/widget.js and clicking in counter button on home page, shows all these actions, which shouldn't fire on clicking button!

One more info I found - such thing happens only if it's first action we do on page that was loaded from ssr. If we change page and return to home, none of previous functions is firing on clicking button.

Source

michalg42

👍6

Most helpful comment

@cjroebuck 's workaround works.

Just upgrade to react-router-redux@4, and update some files following this PR:

https://github.com/erikras/react-redux-universal-hot-example/pull/951/files

pd4d10 on 20 Apr 2016

👍5 ❤1

All 8 comments

michalmikolajczyk on 25 Mar 2016

+1 redux-async-connect seems too unstable, I also faced as issue where data-checksum is not generated, and client.js returns a error if App Component is not connected using asyncConnect

sai-prasanna on 27 Mar 2016

+1 Just faced this issue. This issue seems to be relevant https://github.com/bdefore/universal-redux/issues/91

PanJ on 12 Apr 2016

A workaround for me is to fire blank action at componentDidMount of the App component

PanJ on 15 Apr 2016

👍2

pd4d10 on 17 Apr 2016

+1. also @PanJ your workaround doesn't work for me. just causes the problem to happen earlier, when the App component mounts rather than on the first action fired.