Apollo-client-devtools: Cannot read property 'getStore' of undefined

Created on 18 Mar 2020 · 18Comments · Source: apollographql/apollo-client-devtools

After updating to @apollo/[email protected] (latest), an error is thrown in the console on page load by this extension: Cannot read property 'getStore' of undefined.

It previously worked fine with beta.39.

As there are no source maps, here are some screenshots with the minified code and debugger watch frame:

Source

use-strict

👍55 😕2

Most helpful comment

Same here when updating to @apollo/client 3.0.0-beta.43

matt-senseye on 9 Apr 2020

👍24 😕2

All 18 comments

Same here.

gradinarot on 19 Mar 2020

themarkian on 25 Mar 2020

👍1

Any updates?

themarkian on 25 Mar 2020

👍17

Same problem here.

alfechner on 2 Apr 2020

Same here. Latest version as well.

rolling back to beta 39 made it work for me again. The error was still in beta40.

jebadirad on 6 Apr 2020

Same here when updating to @apollo/client 3.0.0-beta.43

matt-senseye on 9 Apr 2020

👍24 😕2

The same with @apollo/client 3.0.0-beta.44 :(

mzygmunt on 23 Apr 2020

Also having intermittent issues with this

nratter on 23 Apr 2020

+1! @apollo/client@^3.0.0-beta.44

devinhalladay on 28 Apr 2020

👍1

+1! @apollo/client@^3.0.0-beta.44 I had to revert to @apollo/client@^3.0.0-beta.39 in order to see my cache in Apollo Dev Tools

yellowspaceboots on 28 Apr 2020

See:

https://github.com/apollographql/apollo-client/pull/5909#issuecomment-598784949

keithlayne on 30 Apr 2020

👍1

fpsstyle228 on 14 May 2020

beta 48 its still dead

ammanvedi on 17 May 2020

I've created a temporary fork with a hacky workaround. https://github.com/noah-potter/apollo-client-devtools
I've only tested it against a simple app, so it might not work for all cases.

Relevant changes: https://github.com/noah-potter/apollo-client-devtools/commit/52d2b8924236bdb2d2472d761c6fbd1670351804

noah-potter on 18 May 2020

@use-strict Could you try out the latest release of the devtools (2.3.1) and let me know if that resolves the issue?

jcreighton on 3 Jun 2020

👍3 🎉2

@use-strict Could you try out the latest release of the devtools (2.3.1) and let me know if that resolves the issue?

FWIW I'm on 3.0.0-beta.44 and 2.3.1 is working for me (previously broken as per the original post).

willingram on 3 Jun 2020

🎉1

@use-strict Could you try out the latest release of the devtools (2.3.1) and let me know if that resolves the issue?

FWIW I'm on 3.0.0-beta.44 and 2.3.1 is working for me (previously broken as per the original post).

I can confirm it as well. Kudos to the developer 👍