Apollo Client Devtools: Enhance Your GraphQL Experience

Perfect

Works like a charm

It works fine... Saver

Works :)

Extension does not work for Apollo Client 3.9.2 . It simply does not see GraphQL. window.__APOLLO_CLIENT__ is present. It's not a bug with GraphQL. connectToDevTools was EXPLICITLY set to true. App is running in dev mod. window.__APOLLO_DEVTOOLS_GLOBAL_HOOK__.ApolloClient IS present. Yes, my client is created within 10 sec of first load. No, waiting for another 10 sec did not help. "An Apollo Client instance was not found, either because an Apollo Client instance was never created, or because it could not be discovered. This is most commonly fixed by setting the connectToDevTools option to true."

DOES NOT WORK ANYMORE. Uncaught runtime errors: ERROR Cannot convert object to primitive value TypeError: Cannot convert object to primitive value I thought it was something wrong with my app. No, its wrong with this plugin.

Straight up doesn't show up in the UI. No sign of it even being installed, other than seeing in my list of extensions.

My mf proj structure stoped working due to this ext, when I tried to switch between pages

Wasted an entire day trying to figure out why my NextJS 13 app was failing in-app redirects. This was the culprit. Once I removed this, it all worked. The error I hit was "TypeError: Cannot convert object to primitive value" when loading some of my pages.

Do not works between page refreshs, cant trust cache tab. So sad, it is a nightmare to work with cache. Good luck.

Installed in edge, refreshed the page... and can now see queries, execute them in a useful dev environment. Useful.

very sad. it's not working. I hope one day it will work but this is third time coming back realizing not gonna happen

Obnoxiously unnecessary. None of the projects I work on would be needed by this extension... but there's no way to prevent it from showing in the console log. (even if I add a filter, it will still display as a message). Why would the chrome developers force a message that isn't critical to the browser? I guess I'll have to start debugging the console in a different browser now.

I hate it and I hate the fact that I depend on it.

Mixed response. Sometimes the queries/cache populate, sometimes not. Currently its not working at all

Doesn't work at all. Please fix this and update your extension after testing in every browser.

It'a not working on chrome version 120 even

Guys this is not working anymore, even setting connectToDevTools: true, for some reason, version apollo client 3.8.6. Queries work in the app, as well as caching cause i can see it caching with another tool, but nothing is showing in the devtools.

works perfectly fine with Chrome version 120. As others have noted, support must be enabled in your app.

Does not work in the latest Chromium-based MS Edge

Not working at all. With connectToDevTools to true neither

It works fine after setting connectToDevTools to true in ApolloProvider.js (Oct 2023)

It's working but we have to be able to set the column's width, otherwise it's really hard to use the extension

Sorry, it does not work, even if I set: connectToDevTools to true. Also when I add it I get 3 build errors: 2 of them are: "Unhandled Runtime Error TypeError: Cannot read properties of undefined (reading 'getObservableQueries')" And the third is: "Unhandled Runtime Error Error: There was an error while hydrating. Because the error happened outside of a Suspense boundary, the entire root will switch to client rendering." It is on apple silicon and node v16