Redux-devtools-extension: Redux-devtools suddenly not working

[rasmuswoelk]

Hi

I'm a big fan of the redux-devtools extension but lately I have noticed that it stopped working.

It has always worked without problems but now it only shows the @@INIT action when opening the devtools in Chrome. Once I dispatch an action it doesn't record it. The redux actions are functioning correcly.

This is my setup:

• Chrome Version 52.0.2743.33 beta (64-bit)
• Redux 3.5.2
• Redux DevTools 2.0.1
• Recently switched to webpack (could that have an impact?)

I have set it up through my store file like this:

    export default function configureStore(initialState) {
      const store = createStore(
        reducers,
        initialState,
        compose(    applyMiddleware(PromiseMiddleware, ThunkMiddleware, LoggerMiddleware),
        window.devToolsExtension ? window.devToolsExtension() : f => f
        ));

      return store
    }

I have absolutely no idea what is going on since it has always been working fine.
Has anyone else experienced this or could someone maybe point me in a direction. That would be great, thanks!

PS. Great work on the extension. Saves me for a lot of dev hours! 8-]

[zalmoxisus]

Thanks for the feedback and the details. The configuration looks fine.

Please check if it works with our demos to see if it is related specifically to your app. Also try changing the monitor from the top of the extension's window.

[rasmuswoelk]

Hi again

Thanks for the answer :-)

So it is working with the demos. Weird.

Do you mean changning from the Log Monitor to the Chart or what do you mean when you say changing monitor?

The redux-logger is logging just fine. So weird.

[zalmoxisus]

Do you mean changning from the Log Monitor to the Chart or what do you mean when you say changing monitor?

Yes, also try to select instances explicitly (from the second select).

[rasmuswoelk]

Yeah it doesn't seem to work unfortunately. It's something with my setup obviously since it's working in the demos.

[zalmoxisus]

If you could share an example to reproduce, I'd look into it. Or you can run the extension in dev mode. And debug it. It's not that hard because you have to inspect only pageScript.js, which should send changes to the extension's background script.

[rasmuswoelk]

Hi again

I have tried running the extension in dev mode - still not working. Also I tried other computers with other versions of Chrome - same problem.

It's something with my system and I will try to debug it when I have time. I will return if I find anything.

How do I inspect pageScript.js? Can I do it from console?

[zalmoxisus]

@rasmuswoelk, thanks for the details. Most probably it is related to Promise Middleware.

Try to update the store after creating it by adding:

if (window.devToolsExtension) window.devToolsExtension.updateStore(store);

[zalmoxisus]

Just tried simple and complex examples of redux-promise-middleware and it works as expected. If you're sure you don't mutate the state somewhere (you can check it by adding redux-immutable-state-invariant middleware), it would be useful if could fork one of that examples and try to reproduce the issue.

[rasmuswoelk]

Hi again

I was mutating the state in my actions by accident and the redux-immutable-state-invariant found the issue for me.

It is now working!

Thanks for your extensive support and great package for debugging these issues!

[afisher88]

I had this issue (just seeing the @@init) and it turned out I had accidentally created another store instance which the instances dropdown was defaulting to instead of the instance associated with my actions. Removing the duplicate store solved my problem.

[sziebertAu]

Hi everyone,
I just want to share my experience with people in the future who fight with the same issue.
My problem was i accidentally left some deleted constants in the actionsBlacklist. So there was some undefined in the array.
As i removed them, all the actions became visible after the @@INIT.

[MutableLoss]

I just had this happen as well after using the devtools successfully on an app for some time. The only possible change that could have caused this was an update to redux-form and react-redux, and reinstalling/upgrading the devtools package fixed the issue.

[tonymedrano]

Right click Redux DevTools in any position (not inspect) and bam! then back to work, even inspect . 😅