You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have this error while trying to use Next with redux and redux saga.
We use it exactly the same way as the example 'with-redux-saga', and we dispatch an action that triggers a saga in the getInitialProps function:
Is the store in the client the same of the server ? if that's the case you should use a store per request in the server and a single store in the client instead. And if you're using a different store for the client then the dispatch doesn't work as it's going to happen only server side
@hugotox that example is using next-redux-wrapper and it makes sure to create a unique store in the server and a new one for the client by using initStore
I have this error while trying to use Next with redux and redux saga.
We use it exactly the same way as the example 'with-redux-saga', and we dispatch an action that triggers a saga in the getInitialProps function:
When I query the page, it is rendered with the categories displayed, then they disappear and this error is printed in the console...
It all works good when I get the categories through an async await and return them in the props.
More specifically the error reads:
So if I guess correctly the client expects an empty
ul
meaning NO categories and the server renders the list of categoriesVersions:
The text was updated successfully, but these errors were encountered: