Ben Newman

@capaj This will be happening in v3.2.0 as part of #6901, thanks to 03930ee144fb4c053f67c6e1fd8d3a35b2a39ee3.

Unfortunately, I think I spoke too soon, since any fragment's type condition could match a given `__typename` exactly, without any help from `possibleTypes`. This is a problem for identifying (and...

@danfernand One of the things that changed in AC3 is that `cache-and-network` really means to read from the cache _and_ make a network request, not just the first time, but...

We changed a number of things about how `useQuery` and `useLazyQuery` are implemented internally in Apollo Client v3.6, so I would recommend attempting to update with `npm i @apollo/client@latest` when...

I tried the current changes against your [reproduction](https://codesandbox.io/s/usereactivevar-gets-stuck-0hixe3?file=/src/App.js) from #10065 (thanks for that!), and the counter appears to keep updating without getting stuck, so that's good news!

> My question is, my app doesn't have any user data related between requests to apollo, I only use it to fetch data from backend and serve to the user,...

Based on all the great details @Venryx shared [above](https://github.com/apollographql/apollo-client/issues/7964#issuecomment-1027815027), I believe I've made some progress on this problem in PR #9718. Please take a look when you have a chance!...

@Venryx Did PR #9718 make any difference for you? You can run `npm i @apollo/client@beta` to try those changes.

@vedrani You're right, `INVALIDATE` by itself isn't the best fit with a `cache-first` policy, since the invalidated data remain in the cache, so the next cache read usually succeeds, so...

PR in progress for the `reobserveQuery` idea I described above: #7827