Apollo-client-devtools: I can't for the life of me get the debugger tab to appear

Created on 29 Sep 2020  ·  5Comments  ·  Source: apollographql/apollo-client-devtools

I've read all the other issues, and tried everything.

"@apollo/client": "3.2.1"

Chrome Version 85.0.4183.121
MacOS Catalina

I tried the firefox one too.

I'm using expo 39.
window.__APOLLO_CLIENT__ is undefined.
connectToDevTools is true

Any ideas? I really need that cache inspector...

🐞 bug

All 5 comments

@robclouth did you ever get the tab to appear?

I actually just switched to URQL. Lighter and simpler for my use case.
Everything just worked.

On Mon, Jan 4, 2021 at 2:44 PM Donovan notifications@github.com wrote:

@robclouth https://github.com/robclouth did you ever get the tab to
appear?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apollographql/apollo-client-devtools/issues/293#issuecomment-753982501,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJP3ITRYOIKOIGIEIXTKZ3SYHA5NANCNFSM4R6FKBPA
.

@robclouth did you ever get the tab to appear?

Well, I didn't... So still; please advise.

Chrome version 88.0.4324.104 (Official Build) (64-bit)
Apollo Client Developer Tools version 2.3.5
apollo-client version 2.3.7
...also;
connectToDevTools: true

window.APOLLO_CLIENT is undefined, but window.__APOLLO_DEVTOOLS_GLOBAL_HOOK__ is not. window.__APOLLO_DEVTOOLS_GLOBAL_HOOK__.ApolloClient is null, though.

It appears only when I run WEB application locally. This partially solved my problem, but would be curious to know, what webpack/etc. configuration would make it appear for deployed site.

To use Apollo Client Devtools in production, you'll want to pass connectToDevTools: true in as an option to your ApolloClient constructor call. See the devtools config docs for more details. Thanks!

Was this page helpful?
0 / 5 - 0 ratings