React-apollo: [Regression] fetchMore option updateQuery triggers hook update but with previous data

[AlpacaGoesCrazy]

This issue is present again.

Intended outcome:
To get in data object of useQuery hook result of updateQuery function which was provided as option in fetchMore call.

Actual outcome:
Getting in data object in useQuery hook PREVIOUS result of updateQuery function which was provided as option in fetchMore call or original result of a query (if it was the first call to fetchMore).

Version
[email protected] and further releasess

Reproduction
https://codesandbox.io/s/quizzical-goldberg-chfj2

[balovbohdan]

We have the same problem. Any ideas how to solve it?

[balovbohdan]

Maybe related issue. We also get PREVIOUS result here.

https://github.com/apollographql/react-apollo/issues/3640

[iamrommel]

Facing the same issue here

[Emiliano-Bucci]

Any clues on this one? This is a big issue :/

[amannn]

I have the same issue. My current workaround is to keep track of the already fetched pages in a ref and ignore calls to fetchMore if the page is already fetched.

Note that Apollo triggers another render with the correct data.

This is supposedly fixed in the next version: https://github.com/apollographql/react-apollo/issues/3333#issuecomment-577882189.

[Kisepro]

I have the same problem, I can add more information :

• it happens randomly: sometimes after the second calls, sometimes after the fifth, ...
• The network call is the right one: When I inspect the network, the right calls is made on the server but the data received in updateQuery is the previous result

I'm using useQuery from @apollo/react-hooks

[perrosnk]

It's happening when usingfetchPolicy: 'cache-and-network'.
I am running on the latest v.3 beta.48