-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
3.5.0 network request hangs pending. rolling back to 3.4.17 fixes an issue. 3.5.9 issue persists, #9456
Comments
I'm also getting this.. is there any solution? |
@damiangreen for now the only solution to roll back to 3.4.17 |
Are you by any chance using |
Yes we are using |
@damiangreen You wouldn't have to remove useLazyQuery(query, {
ssr: false,
...otherOptions
}) |
thx ill give it a go |
Also running into queries randomly hanging when using Noticed this on It seems that downgrading to This seems of critical priority. Edit: Nevermind, my issue is probably a different one. All versions up to 3.6.2 seem fine. It's just on 3.6.3 that this happens in my case. Opened #9690 instead |
Thanks for reporting this! It sounds like #9690 is the issue we should look at, and this particular problem has been resolved with subsequent releases? We are currently at release 3.6.6 So if you haven't upgraded to the newest release, give it a try to see if it resolves these issues. |
Fixed in 3.6 |
Intended outcome:
correct network request execution
Actual outcome:
request hangs in pending state.
How to reproduce the issue:
I'm not sure how to reproduce. We had cached this error while updating @apollo/client@3.4.16 to 3.5.9. I've tested other versions and the bug appears in 3.5.0 and consists in every version till current at the time of writing 3.5.9.
We have nextjs@12.1 app, and we are requesting graphql on server-side with React.js hook, generated by @graphql-codegen/cl@2.6.2
Versions
Thank you for a great work!
The text was updated successfully, but these errors were encountered: