apollo-client-devtools: Client does not appear in Chrome
I’m using Mac Chrome version
Version 75.0.3770.100 (Official Build) (64-bit)
Client Version 2.2.3
Apollo client has suddenly stopped working. shows blanks.
Whether I keep connectToDevTools: true,
or don’t include it, there is no effect. In any case window.__APOLLO_CLIENT__
is available in console.
npm package "react-apollo": "^2.1.4",
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 17
- Comments: 20 (1 by maintainers)
Disable react dev tools and refresh, Apollo working fine, maybe there is a conflict between two of them
Started to face this problem from about a week now. It now works after adding
connectToDevTools: process.env.NODE_ENV !== 'production'
line in ApolloClient constructor of my react app. Doesn’t conflict with react-dev tools extentions.+1 on the disabling react dev tools. Why is this issue closed? This hasn’t been solved
One reason you don’t see the “Apollo” tab is that maybe you are inspecting production (npm run build) and not the development mode (npm run dev)
Facing this issue. Disabled all the extensions except Apollo devtools but the chrome dev tools doesn’t show on my React app. However on Apollo studio it is shown on the chrome dev tools.
This should be resolved as of the latest release (2.3.1).
I’m having a similar issue, but for me
window.__APOLLO_CLIENT__
returnsundefined
, even withconnectToDevTools: true
in the constructor. @samithf’s suggestino did not work.Thank @MuizNadeem. Setting
connectToDevTools
worked for me as well. Disabling other extensions made no difference in my case.There is a conflict between React Dev Tools and Apollo Dev Tools, I tried to disable React Dev Tools and restart chrome dev tools and Apollo tab showed up.
Disabled the React Dev Tools still, the Apollo tab doesn’t appear. Windows 10 Google Chrome Dev Version 106.0.5231.2 (Official Build) dev (64-bit).
omg wth. disabling react dev tools worked for me. that’s weird… Thank you for the suggestion!!!
This works for me, There must be a conflict with the react and apollo tooling.
For anyone using
apollo-link-rest
exclusively (i.e. they do not have agraphql
server at all) please have a look at #228.