Skip to content
This repository has been archived by the owner on Mar 13, 2020. It is now read-only.

[Redux DevTools] Uncaught Error: You may not call store.getState() while the reducer is executing. #275

Closed
Dabolus opened this issue Nov 28, 2018 · 2 comments

Comments

@Dabolus
Copy link
Contributor

Dabolus commented Nov 28, 2018

Currently, the Starter Kit is not working at all because of an "Uncaught Error":

image

This issue is not related to the Starter Kit itself, but it is caused by the latest version of Redux DevTools Extension. I'm creating this issue just to keep track of this so that folks that are going to try the Starter Kit now know why this is happening.

While the issue gets fixed on Redux DevTools extension, these are the things you can do to make it work correctly again:

  1. Temporarily disable or uninstall Redux DevTools Extension
  2. Manually downgrade Redux DevTools Extension to version 2.15.5 (which isn't affected by this issue) by following these steps:
    • Download Redux DevTools Extension version 2.15.5 from here
    • Extract it to some folder
    • Open chrome://extensions
    • Turn on developer mode from top left
    • Click on Load Unpacked and select the folder containing the extracted extension
  3. If testing the Starter Kit locally, temporarily disable (or completely remove) Redux DevTools Extension from src/store.js:24:
    - const devCompose = window.__REDUX_DEVTOOLS_EXTENSION_COMPOSE__ || compose;
    + const devCompose = /* window.__REDUX_DEVTOOLS_EXTENSION_COMPOSE__ || */ compose;

Related issue: zalmoxisus/redux-devtools-extension#588

@keanulee keanulee changed the title Uncaught Error: You may not call store.getState() while the reducer is executing. [Redux DevTools] Uncaught Error: You may not call store.getState() while the reducer is executing. Nov 28, 2018
@Dabolus
Copy link
Contributor Author

Dabolus commented Nov 28, 2018

Closing this as Redux DevTools Extension 2.16.3 has been released on the store and the issue has been fixed (how fast!)

@Dabolus Dabolus closed this as completed Nov 28, 2018
@frankiefu
Copy link
Member

@Dabolus Thanks for the quick report and the detailed workaround. And then followed up with the fix on their end. We really appreciate it.

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

No branches or pull requests

3 participants