Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Getting Error on my application with new version v 2.16.0

See original GitHub issue

Error: You may not call store.getState() while the reducer is executing.

Issue Analytics

State:
Created 5 years ago
Reactions:222
Comments:124 (8 by maintainers)

Top GitHub Comments

107reactions

bpotecommented, Nov 28, 2018

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://extensions and turn on developer mode from top left and then click on Load Unpacked and select the extracted folder for use.

54reactions

zalmoxisuscommented, Nov 28, 2018

Fixed 2.16.1 was published on Chrome Store and will be available in an hour. Sorry about that, it worked on Redux 3, but throws on 4.

Top Results From Across the Web

java - @Slf4j logger not working after updating to 2.16.0 version

1. Check the output of mvn dependency:tree if you still have some conflicting Log4J versions in there. · generally the only way NoSuchMethodError ......

Log4Shell: RCE 0-day exploit found in log4j, a popular Java ...

On Thursday, December 9th a 0-day exploit in the popular Java logging library log4j (version 2), called Log4Shell, was discovered that ...

Impossible to update from 2.16.0 - Support - Mautic Forums

Hello there, I have got the same error on my side, on Ubuntu Server 18.04 running with PHP 7.2. I tried to update...

Upgraded to log4j 2.16? Surprise, there's a 2.17 fixing DoS

To fix the vulnerability, log4j version 2.17. 0 (for Java 8) has been released today and allows only "lookup strings in configuration" to ......

Log4J2 Vulnerability and Spring Boot

I had to maintain a legacy project and the "log4j2.version" property DID NOT work. I was still getting the vulnerable version for the...