Apollo Client Devtools

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,... Show more

Apollo TeamDeveloperJun 24, 2024

Hey Andrii. Would you mind creating an issue in our extension repo (link below)? We'd love to investigate further and understand what might be happening here. This most certainly sounds like a bug, but its a bit difficult to tell what might be happening here without more info. Any more information you can provide would be helpful. Thank you! https://github.com/apollographql/apollo-client-devtools/issues/new?assignees=&labels=&projects=&template=bug_report.md&title=

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.

Apollo TeamDeveloperJun 24, 2024

Hey there! So sorry about this! There are a couple things at play here that I believe are causing this issue. 1. The root error is caused by a bug with Apollo Client 3.8.0 - 3.8.9 with the release of error minification in production builds. The arguments weren't serialized correctly causing this error to appear. This was fixed with https://github.com/apollographql/apollo-client/pull/11483 which was released with 3.8.10. Try upgrading your Apollo Client version and that should help. 2. We added the ability for the devtools to interpret the minified error messages so that you see the actual error messages in your console. Unfortunately due to the bug in Apollo Client, it seems this made its way to the extension as well. We are aware of this issue and are tracking it in https://github.com/apollographql/apollo-client-devtools/issues/1328. I think there are some things we can do in the extension to try and avoid the error and make this more helpful. Sorry again for the issue! Hope the upgrade of the client helps here.

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

Apollo TeamDeveloperJun 24, 2024

Hey there! So sorry to hear you're having issues with this? What version of the devtools are you using? We released an update some time ago that should always create the devtools panel, regardless of whether it detects a client instance or not. If you're not even getting this far, it sounds like a serious issue that we should look at further. Would you mind opening an issue in our extension repo so we can investigate further? Any more details you can provide would be super helpful. Thanks! https://github.com/apollographql/apollo-client-devtools/issues

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

Apollo TeamDeveloperJun 24, 2024

Hey there! Would you be willing to open an issue in our GitHub repo with the issues you're seeing? We'd love to dig in further to understand what's not working for you so. Thanks! https://github.com/apollographql/apollo-client-devtools/issues

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.

Apollo TeamDeveloperJun 24, 2024

Hey there! So sorry about this! There are a couple things at play here that I believe are causing this issue. 1. The root error is caused by a bug with Apollo Client 3.8.0 - 3.8.9 with the release of error minification in production builds. The arguments weren't serialized correctly causing this error to appear. This was fixed with https://github.com/apollographql/apollo-client/pull/11483 which was released with 3.8.10. Try upgrading your Apollo Client version and that should help. 2. We added the ability for the devtools to interpret the minified error messages so that you see the actual error messages in your console. Unfortunately due to the bug in Apollo Client, it seems this made its way to the extension as well. We are aware of this issue and are tracking it in https://github.com/apollographql/apollo-client-devtools/issues/1328. I think there are some things we can do in the extension to try and avoid the error and make this more helpful. Sorry again for the issue! Hope the upgrade of the client helps here.

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

Apollo TeamDeveloperJun 24, 2024

Hey there! I believe this should be fixed with version 4.13.1 or later of the devtools. https://github.com/apollographql/apollo-client-devtools/pull/1378 did some work to fix some of the issues with page refreshes and data not showing up. If you have upgraded and are still seeing this issue, do you mind creating an issue in our repo for us so we can dig in further? Thanks! https://github.com/apollographql/apollo-client-devtools/issues