redux-devtools-extension Since this morning I'm getting "No store found. Make sure to follow the instructions."

So I refresh the app
I see the redux actions for a second
90% of the times I see "No store found. Make sure to follow the instructions."

I use the same app version of last night and was working.

Aug 14 '18 06:08 hackhat

Some questions to try and help diagnose:

Is this in Chrome, Firefox or both browsers? Is your redux store large (or can it vary in size)? Do you see any errors if you run with pause on exceptions (including caught exceptions) enabled?

Aug 19 '18 00:08 mbtts

Chrome. Store has less than 1500 objects, no errors. Works randomly

Aug 19 '18 05:08 hackhat

Me too, and I believe the timing is about the same. About a week ago Redux dev-tools starting crashing and it cannot load the chart very quickly. It reacts really poorly to state changes, even if the changes are really simple.

It worked flawlessly the week before, with the same app I'm working on right now, which does not have any significant changes to the store.

Chrome 68.0.3440.106 on OS X 10.13.6.

Aug 20 '18 19:08 mrdj07

So I'm still get randomly this issue

Aug 20 '18 20:08 hackhat

Thanks @hackhat. The reason I was asking was to see if it was related to #543, however from your description this is unlikely to be the case.

Aug 20 '18 21:08 mbtts

I'm sorry it's been an error on my part. Actually there was a significant modification made to the store, not to my knowledge at the moment of reporting. Fixing the issue on my end fixed the problem, though I had the exact same error as @hackhat. A developper added a gigantic JSON file as a require() to an initial state. This caused the issue.

Aug 21 '18 17:08 mrdj07

Looks like if I refresh, I quickly move to another tab, come back to my app, the redux dev tools, can't find the store. I can reproduce many many times.

Aug 31 '18 18:08 hackhat

Also sometimes I can see the redux store for 1 second and then it says there is no store.

Sep 01 '18 18:09 hackhat

Now it happens so many times I can't work anymore.

Sep 03 '18 10:09 hackhat

Following up on this as well. It seems to randomly vary between working fine when I refresh or I see a flash of the actions list for a split second before it disappears to the "no store found" error.

Oct 09 '18 22:10 ghost

I have the same problem. Directly after loading the devtool UI is displayed properly. After about 1 second it disappears and "No store found. Make sure to follow the instructions." is displayed. Happens on Chrome 65.0.3325.181

Oct 15 '18 09:10 elsueno

We have the same problem No store found. Make sure to follow the instructions. occurs a lot now (Chrome 69) when clicking on the redux devtools tab in chrome devtools. Of course it is initialized correctly. Either it doesn't appear right away or it disappears after a second as described above. It only seems to work again after closing and reopening Chrome devtools AND reloading of the page until it stops working again after a few page reloads (randomly).

Just wanted to mention that when it is working the plugin is unresponsive for ~10 seconds on page load.

Is our store too big? Its a 70K lines object (around 2.3MB of data) and we are launching around 100 actions on page load. Or could anything else in our store cause these issues? Are there any settings where we could adjust that?

Oct 16 '18 12:10 alk-jerber

Ok it seems to work when you right click and select Reload Frame

Oct 26 '18 14:10 alk-jerber

I've been having the same issue seeing "No store found" in Chrome since sometime in March. It's only gotten worse, and seems to be random when it happens. I've been seeing it at work, and our clients only use Chrome, so I haven't verified if it happens in other browsers.

I'd like to see if a debug mode could be activated for the plugin. If I could log something on crash and either examine it myself or send it to the Redux Devtools Extension team, we could swiftly resolve this issue.

Does such a mode exist?

Oct 26 '18 19:10 Sawtaytoes

Experiencing similar. When I have a redux app open, and open the redux devtools, things work fine. But as soon as I refresh the page, I get the "No store found" message.

In order to get the store back in the tools, I have to close Chrome DevTools and reopen the them and then go back to the Redux panel. Extremely annoying to say the least.

At least the workaround above seems to work, so now just right click and choose to reload the frame. Thanks @johanneserber !

Nov 05 '18 17:11 RavenHursT

Looks like the problem is that Redux store was created before Chrome injected extension's script, so window. REDUX_DEVTOOLS_EXTENSION doesn't exist to include in the compose. We are relying on the fact that Chrome injects extension script begore executing app script and it happened so most of times. Seems the problem appears more often from recent Chrome versions.

The best way to handle this for a app is to create the store asynchronously, so you can be sure that extension's script is executed before. Also in this way you can persist initial state from localStore. But of course it doesn't fit all use cases.

We can just add the workaround suggested above to the message. Any other thoughts on this?

Nov 17 '18 13:11 zalmoxisus

In 2.16 reload workaround wouldn't be necessary, it will land in a day on Chrome Store. I'll implement a pooling method and the ability to autoreload the page injecting page script in 3.0 so it should be more stable.

Nov 27 '18 21:11 zalmoxisus

@zalmoxisus I know this issue has been closed now, but FYI: This "reload frame" workaround was still necessary for me with v. 2.17.0 / Chrome Version 75.0.3770.100

  "dependencies": {
    "@angular/animations": "~7.2.0",
    "@angular/common": "~7.2.0",
    "@angular/compiler": "~7.2.0",
    "@angular/core": "~7.2.0",
    "@angular/forms": "~7.2.0",
    "@angular/platform-browser": "~7.2.0",
    "@angular/platform-browser-dynamic": "~7.2.0",
    "@angular/router": "~7.2.0",
    "@ngrx/effects": "7.4.0",
    "@ngrx/store": "7.4.0",
    "@ngrx/store-devtools": "7.4.0",
    "core-js": "^2.5.4",
    "rxjs": "~6.3.3",
    "tslib": "^1.9.0",
    "zone.js": "~0.8.26"
  },

Jul 02 '19 11:07 arturhun

Have the same issue in Firefox and Chrome

Aug 27 '19 12:08 akamensky4xxi

I had an older version of the extension installed. Removing the Chrome extension and re-installing it worked for me with Chrome 76.0. Chrome's auto-updating of extensions either didn't happen or failed somehow in this case.