New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Again, onCompleted is not called when useLazyQuery #11714
Comments
Hi @zvitek, you write
and then you write
so I have to admit, I'm a bit confused: Is it being called, or is it not being called? |
I'm sorry. |
@zvitek without a reproduction its a bit difficult to understand what might be happening here. This seems pretty standard usage of the hook. That being said, what happens if you remove the |
@jerelmiller |
What version of |
Hey @zvitek 👋 Just a quick nudge on this issue, any chance you could provide us some more information and a reproduction that shows the issue here? |
We're closing this issue now but feel free to ping the maintainers or open a new issue if you still need support. Thank you! |
Hey. Hey,
I know this has been brought up a few times. I looked at the history of issues and tried all the combinations.
But I can't get to the state where onCompleted is called on useLazyQuery and I don't know what to try next.
I have the following simple call in hook
When I call the syncNotifications function, the console calls the request, which returns the correct status 200 and the contents in the payload.
However, even if the request is correct, the onCompleted callback is called and the load is still in true state and data are undefined.
I also tried pure useQuery, but the same result.
I tried different settings and combinations of fetchPolicy as notifyOnNetworkStatusChange. But none of them helped.
I have tried older versions as well. Nothing.
The call is made within React Native, but I don't see that being an issue there.
Anyone else have any idea where the problem might be?
Thank you a lot!
The text was updated successfully, but these errors were encountered: