Open sschneider-ihre-pvs opened 3 years ago
@sschneider-ihre-pvs any chance you could provide a small runnable app that this happens with, to help with troubleshooting?
I think not since it is an internal project. Is there any way to get you some extra information that could be relevant? What could cause queries to disappear? Is there a log file or something?
I also have in an internal project the same behavior where some (not all) queries are disappearing after few seconds.
Same thing happens in my app - queries only stay in the queries tab for less than a second or so.
Perhaps it's due to older versions of apollo-client and friends?
This app is on:
"apollo-cache-inmemory": "1.5.1",
"apollo-client": "2.5.1",
"apollo-client-preset": "1.0.8",
"apollo-link": "1.2.11",
"apollo-link-context": "1.0.14",
"apollo-link-http": "1.5.11",
"apollo-link-ws": "1.0.17",
"apollo-utilities": "1.3.2",
Same thing happens in my app - queries only stay in the queries tab for less than a second or so.
Perhaps it's due to older versions of apollo-client and friends?
This app is on:
"apollo-cache-inmemory": "1.5.1", "apollo-client": "2.5.1", "apollo-client-preset": "1.0.8", "apollo-link": "1.2.11", "apollo-link-context": "1.0.14", "apollo-link-http": "1.5.11", "apollo-link-ws": "1.0.17", "apollo-utilities": "1.3.2",
i have "@apollo/client": "^3.2.3",
and having the same problem.
they show then vanish after a second
Having same issues. It seems to be more complicated (at least in my case): Active Queries are duplicated, they are almost identical, but one has __typename
in it. And the one that has __typename
disappears when I navigate from the page. What's even worse, when i try to refetch this query, I get a warning about Unknown query
which causes issues with updating cache
I'm still getting this issue, any updates?
Hey @harveyconnor 👋
No updates yet. This is on our radar and we'd like to get to this in the near term.
To get this working, we'll need to introduce changes to Apollo Client itself so that we can capture the "one-off" requests that happen in the client. Currently the extension works by reading some internal state off the client, but that internal state only holds active queries. One-off queries aren't maintained in that state and we have no way of capturing that information otherwise, hence why this is still an outstanding issue.
We are still exploring how best to introduce code in Apollo Client core for devtools without bloating its bundle size too much. We've got a lot of ideas on features to add but haven't had the time to really sit down and figure out exactly how we want to tackle that. As soon as we do, this is one of the top things we'd like to fix.
I know its not a great answer, but hopefully that provides some context around the issue.
Intended outcome: Queries should stay in the list after they have finished so they can be replayed in graphiql
Actual outcome: Queries vanish.
How to reproduce the issue: Currently happens everywhere I tried to use Apollo Devtools
Desktop (please complete the following information):