redux-devtools-extension: Getting Error on my application with new version v 2.16.0
Error: You may not call store.getState() while the reducer is executing.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 221
- Comments: 124 (8 by maintainers)
Commits related to this issue
- Rollback dynamic maxAge as Redux 4 doesn't allow calling getState Related to #588, #592, #590 — committed to zalmoxisus/redux-devtools-extension by zalmoxisus 6 years ago
- Check if filter from option page was injected Related to #588, #591 and #589 — committed to zalmoxisus/redux-devtools-extension by zalmoxisus 6 years ago
- Pass lifted state to workaround the limitation on calling getState in Redux 4 Related to zalmoxisus/redux-devtools-extension/issues/588 — committed to zalmoxisus/redux-devtools-instrument by zalmoxisus 6 years ago
- Bring dynamic maxAge back Related #588 — committed to zalmoxisus/redux-devtools-extension by zalmoxisus 6 years ago
- Get liftedState from instrumentation instead of calling getState Related #588 — committed to zalmoxisus/redux-devtools-extension by zalmoxisus 6 years ago
- Add to README how to load the extension from gh releases Related to #588 — committed to zalmoxisus/redux-devtools-extension by zalmoxisus 6 years ago
In case anyone is looking for temporary work around(for chrome), you can download https://github.com/zalmoxisus/redux-devtools-extension/releases/download/2.15.5/extension.zip and then extract it to some folder.
Type
chrome://extensionsand turn on developer mode from top left and then click onLoad Unpackedand select the extracted folder for use.Fixed
2.16.1was published on Chrome Store and will be available in an hour. Sorry about that, it worked on Redux 3, but throws on 4.2.16.1is available on Crome Store. Please let me know if it helps.Looks like it’s specifically from this line a commit added earlier today.
(Also, folks, please stop with the +1 comments - that’s what “reactions” are for.)
+1 same issue
Shipped
2.16.2which should fix the issue with ngrx, it should be available on Chrome Store in an hour. Please refer to #589 for that issue.+1 same issue
same issue
No testing before making an update? I don’t want this extension anymore, good bye forever
+1 It coincided with Chrome updating to version 70.0.3538.110
Same
Published
2.16.3and it’s available now on Chrome Store. If someone still experience any issues, please let me know.Sorry for the troubles and thanks to everyone who helped here! If you downgraded to
2.15, it’s highly recommended to update to the last version as it includes many fixes and improvements in performance. We rarely need to change anything onredux-devtools-instrumentpart which would affect the client app (without opening extension window). It would be much appreciated, if you can help check the releases for your use case before we ship them to Chrome Store.+1 with Chrome 70.0.3538.110 save us! 😦
+1
+1
+1
+1
+1! Spent 3 hours to find exact reason why.
+1
+1
+1 almost gave up on chrome
+1
It’s astonishing how many people keep commenting “+1” when they’ve been asked a million times to not do that and instead use Github’s upvote feature that was created specifically to eliminate this problem.
+1 with Chrome 70.0.3538.110
v2.16.1 is GOOD!
For anyone having the issue described in this ticket, just go to chrome://extensions and “update” (in developer mode) then verify that “Redux DevTools” extension is showing “2.16.1” (not 2.16.0!)
For those who had previously disabled the extension, just re-enable it and verify the version number and update it if necessary.
Thanks to the quick fix for this bug, hopefully these types of errors will be caught before release in the future.
+1
+1 xD
I temporarily get around it by manually loading extension at the version of 2.15.5.
+1.5
+1
What is worse is, that it breaks sites using redux, which did not turn off redux-dev-tools in production modes (they exist apparently - atlassian bitbucket).
+1
+1 same here
Yes.
+1
It worked for me ! thanks
+1
+1
+1
+1 same
@zalmoxisus Not fixed for me with NGRX 6.1.x
+1
+1
I love wake up to those “breaking issues” 😭
+1 the same problem
+1
+1 same issue
Not solved for me. I got version 2.16.2
Fixed. Thanks for the reactivity. We use it everyday in our dev stack and we forget it. And we also forget it’s free. So a very big thanks for your work !
Nope - not for me either. Running 2.16.1 now… same whitelist error
Read the rest of the comments… Disable the Redux devtools chrome extension (2.16.0)
+1
+1
+1
+1
+1
+1
+1 same h3re
+1
Same here +1
+1
+1
Love auto updates.
+1
+1 Same
+1
@zalmoxisus Just finish to test version 2.16.3 all work for me 😃 Thank you
@rubenpro could you please provide more details about the error you’re getting and if possible a repro?
Same issue… Lovely morning! 😃
Like @nuclearspike said: Disable the Redux devtools chrome extension (2.16.0), works like a charm
+1
+1
+1
+1
+1
+1
+1
+1
how to back v2.15.5 in chrome extension?
+1
+1 Same
+1 Same
+1 Same
+1 Same
+1