Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug]: initial state is undefined after having r/devtools open and refreshing #616

Closed
iamclaytonray opened this issue Dec 20, 2018 · 1 comment

Comments

@iamclaytonray
Copy link

Steps to reproduce

Have chrome dev tools open and select the redux tab. Play around with some state (dispatch an action or something). Refresh. State in devtools is now undefined.

It's also important to note that while the dev tools shows state as undefined, my application works fine. I'm able to dispatch actions and see data updated. I'm able to get data from state. It just doesn't show

Specs

  • MacOS Mojave 10.14.2
  • Chrome 71.0.3578.98 (Official Build) (64-bit)
  • All redux-related deps are the latest and greatest.
  • I don't use redux devtools (the deps). I just use the one liner because I'm lazy like that

I haven't used Redux in several months but it was working properly last time. Unfortunately, because I haven't used Redux (and thus, redux devtools), I'm not sure when this bug was released. Sorry!

screen shot 2018-12-20 at 12 58 30 pm

But if I close chrome devtools, refresh the page, open up chrome devtools again, and go to the redux tab, I have my state back. I can share a screenshot if needed.

@iamclaytonray iamclaytonray changed the title [bug]: initial state is undefined after having it open and refreshing [bug]: initial state is undefined after having r/devtools open and refreshing Dec 20, 2018
@zalmoxisus
Copy link
Owner

zalmoxisus commented Dec 20, 2018

Thanks for the report! Can you reproduce it with out todomvc demo? If not, a demo I could run to reproduce (on jsfiddle, codesandbox... or repo) would be helpful to look into. It also uses one-liner. I tried the specified steps and it doesn't lose the state there. Looks like in your case it got an exception in a react component, that's why it was working after closing and reopening.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants