-
Notifications
You must be signed in to change notification settings - Fork 787
Multiply useQuery
calls no longer always share updated results
#3262
Comments
Could you make codesandbox? |
@patroza As mentioned in #3262 (comment), is there any chance you could create a small runnable reproduction that demonstrates this? |
Alright guys, will try to make that work this week. Things are a bit crazy here atm, wrapping up work before getting married and going on a holiday. |
Congratulations @patroza! If you don't have time, no worries. |
Hi I'm encountering similar issue here. I have a I took a trace and I think this line is suspicious: I tried to print some console log here, and I found that when Apollo cache was updated, this I'm not sure how This still seem to happen to me in 3.0.0 public release. |
@zhusee2 Any chance you can put tougher a reproduction that shows this? |
Sorry it's my bad. It looks like a part of my code tries to update cache in Here's the ref about |
We'll close this for now, but if anyone encountering this can supply a small runnable reproduction, we'll re-open. Thanks! |
Intended outcome:
With two separate calls to the same query, I expect if I refresh one of them, that the other query result is also updated
Actual outcome:
1 query updates, the other one doesn't. So far it seems to work for 1-2 requests, but at the 3rd it stops working, and the data desynchronizes.
How to reproduce the issue:
I call
useQuery
for the same query at 2 places.I have 1 mutation, that will update the query content in cache, after mutation execute, through
Version
Latest Apollo 3 beta.
It worked fine on the previous beta.
The text was updated successfully, but these errors were encountered: