Apollo console doesn't appear sometimes

[danielo515]

I have the apollo dev-tools installed on chrome. Sometimes the apollo dev tools appear the same way React components and Redux does, but many times it doesn't appear. I don't know why, and it's very frustrating

Intended outcome:

I expected the apollo console to always appear, even if it has to show an error

Actual outcome:

No apollo console

How to reproduce the issue:

I wish I know what causes this, but I have no idea

Desktop (please complete the following information):

• OS: MacOs
• Browser Chrome
• Browser version 90.0.4430.212
• Extension version 3.0.5

[ajaypillay]

I face the same issue as well. OS: Fedora 32 64-bit Browser: Chrome Browser Version: Version 91.0.4472.77 (Official Build) (64-bit) Extension Version: 3.0.5

Sometimes I can fix this by closing the entire Chrome Dev Tools and/or closing and opening a new tab and opening up the dev tools again, then the Apollo tab appears.

It's quite erratic and unfortunately I can't provide more information as I'm not able to accurately consistently reproduce it.

For now I close and reopen the tab/Chrome Dev Tools until the Apollo tab appears.

That being said, the GraphiQL tab in Apollo Dev Tools shows up completely blank all the time, even though I can open up Graphiql at localhost:3000/graphql or XXX.XXX.XX.XX:3000/graphql.

EDIT: To elaborate more on the current behavior, if Apollo Dev Tools doesn't load, I close the Chrome inspector, reload the page, and then open the inspector back up, and then the Apollo tab appears. Then, I can access everything except GraphiQL. When I click on GraphiQL, it's just a blank page, nothing shows up nor are there any errors thrown.

EDIT2: As of 13 Aug 2021, I am able to see GraphiQL in the Apollo Dev Tools. Extension Version is still 3.0.5.

[oirodolfo]

It's happening with me a lot, unfortunately... The Apollo tab doesn't even appear most of the time.

---

• OS: macOS
• Browser: Chrome & Chrome Canary
• Browser version: 93.0.4544.0 (but it also happens in Chrome 90)
• Extension version 3.0.5

[floriancargoet]

It's happening to me today… Fixed by restarting Chrome entirely, devtools restart or incognito mode weren't enough.

[MurzNN]

Same problem with Firefox and Chrome on Linux too :-(

[Nightbr]

Same on Firefox and Chrome on Linux Mint (recently). And when the tabs Apollo is present, there is nothing in it (no cache, no active queries).

Seems an update in Firefox & Chrome has broken the extension.

• Linux Mint 20.2 Uma base: Ubuntu 20.04 focal
• Firefox 90.0.2 (64 bits)
• Chrome Version 92.0.4515.131 (Build officiel) (64 bits)

On Chrome I have an error:

Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.

• https://stackoverflow.com/questions/54619817/how-to-fix-unchecked-runtime-lasterror-could-not-establish-connection-receivi
• https://stackoverflow.com/questions/54181734/chrome-extension-message-passing-unchecked-runtime-lasterror-could-not-establi/54686484#54686484

Seems it needs a fix with the latest Browser version

[Nightbr]

Try it on a Macbook Pro:

• Chrome Version 92.0.4515.131 (Build officiel) (x86_64)
• Firefox 90.0.2

Same issue. Not related to OS but really related to new browsers update. Any chance an Apollo team member take a look at this, this Devtool is really useful to debug the Cache and Active Queries.

thanks for your help!

[hwillson]

Thanks for the details everyone, and sorry for the delay. We're looking into this.

[austinbiggs]

Any follow-up here? :)

[steezeburger]

Mine never appears. I've had it installed for a year and completely forgot I had it because I don't think I've ever actually seen it load. I've tried lots of things and cannot get it to ever appear unfortunately :/

[Nightbr]

is there a workaround to debug Apollo cache without the browser extension? If anyone has a solution it could be a great workaround until this is fixed. thanks a lot :pray:

[awarrenlove]

@Nightbr You should be able to see what's in the current client cache by looking at window.__APOLLO_CLIENT__.cache.data.data.

[Nightbr]

@awarrenlove This is weird because this object is empty:

EDIT: I found my problem, if you have several instance of ApolloClient define in your app, it is the latest created that is linked to DevTools.

I had something like this:

export const graphQLClient = new GraphQLClient();
export const graphQLPublicClient = new GraphQLClient(true);

Which creates several instances of ApolloClient. I find a way to have only one ApolloClient instance and use paramters to remove token or header for auth (Public VS Auth client).

[trdaya]

The issue still exists on Browser - Chrome Version 94.0.4606.81 (Official Build) (x86_64) OS - macOS Catalina Version 10.15.7

After some trial and error, a temporary fix that I found was to: Disable the extension -> Go back to the website -> Close DevTools -> Refresh the page -> Enable the extension -> Go back to the website -> Refresh the page -> Open DevTools to find the Apollo extension there

[mikaelgramont]

It sure would be nice to be able to use this extension, but every time I reach for it, it's nowhere to found in my developer tools.

[ViktorCoder]

Fixed it by changing the settings of this extension (Site access)

[Richacinas]

Same as @ViktorCoder. I allowed all sites on the Site Access settings (in Spanish here):

[davemeehan]

Unfortunately none of these work-arounds have worked for me. Any update on this @hwillson? Osx 12.0.1

Doesn't work: Chrome: Version 96.0.4664.93 (Official Build) (x86_64) Brave: Version 1.32.115 Chromium: 96.0.4664.93 (Official Build) (x86_64)

DOES work in Firefox: 94.0.1 (64-bit)

[trev125]

The issue still exists on Browser - Chrome Version 94.0.4606.81 (Official Build) (x86_64) OS - macOS Catalina Version 10.15.7

After some trial and error, a temporary fix that I found was to: Disable the extension -> Go back to the website -> Close DevTools -> Refresh the page -> Enable the extension -> Go back to the website -> Refresh the page -> Open DevTools to find the Apollo extension there

This is the only thing that has worked for me on MacOS and Firefox. Would love to not have to do that everytime though

[Damien-Burke]

Same problem in Firefox 98.0.1 /MacOS. Simply does nothing. Workarounds above do not work.

[onpaws]

Just happened to me again. This issue seems to have become worse with the v3 release.

I notice that the React extension by comparison seems pretty reliable at loading itself. I'm ignorant of web extension initialization context, but would like to suggest to whoever is maintaining this extension, there could be some useful lessons to glean there.

[Richacinas]

The only thing that works for me 90% of the times is:

• close tab and open new one.
• load your website and wait a little bit until it is "still" (Apollo operations are done).
• F12 and check it out. The Apollo tab should appear this time.

[atapas]

Doesn't work At All.

[SadmanYasar]

Facing this exact issue. It shows up on the Apollo Studio but not on the React app. Tried the workarounds but did not work.

[sethc2]

Also has recently stopped working for me and other engineers I work with on both chrome and firefox.

I am able to get it to work if I add connectToDevTools: true where I new up our ApolloClient, but previously window.__APOLLO_CLIENT__ showed up without having to do this.

[juanlet]

Also has recently stopped working for me and other engineers I work with on both chrome and firefox.

I am able to get it to work if I add connectToDevTools: true where I new up our ApolloClient, but previously window.__APOLLO_CLIENT__ showed up without having to do this.

That is the solution, in fact they added it in their docs

https://www.apollographql.com/docs/react/development-testing/developer-tooling/

Configuration While your app is in dev mode, the Apollo Client Devtools will appear as an "Apollo" tab in your web browser inspector. To enable the devtools in your app in production, pass connectToDevTools: true to the ApolloClient constructor in your app. Pass connectToDevTools: false if want to manually disable this functionality.

[hwillson]

Hi all - this issue is being tracked in multiple places. See https://github.com/apollographql/apollo-client-devtools/issues/924#issuecomment-1276793942 for the latest update.

[alessbell]

Hi all 👋

Both the devtools and @apollo/client have put out recent releases with various improvements to the registration mechanism that should resolve this issue.

Please ensure you are running the devtools at version 4.1.5 or greater and Apollo Client at version 3.8.3 or greater so I'll close out this issue. Please create a new issue to report any other bugs you may encounter, thanks :)