Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Network error is not reported in errors and loading stays true

See original GitHub issue

When useing useQuery (with suspense false), I get a network error, but the hook state stays with “loading: true” and errors undefined. networkState is still 1.

Issue Analytics

State:
Created 5 years ago
Reactions:2
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

mateusznowosielskicommented, Dec 24, 2018

Thanks @umidbekkarimov this is very helpful. Error gets properly handled, I also checked the skip option and I like the new typescript aspect. Hope it gets merged.

1reaction

avocadowastakencommented, Dec 23, 2018

@mateusznowosielski can you check https://npmjs.com/@dc0de/react-apollo-hooks, it’s published version of #42.

Top Results From Across the Web

Loading state stuck true forever · Issue #2669 - GitHub

If I send a query and get 404 error in response then everything will be ok and request state will change to loading=false...

Handling operation errors - Apollo GraphQL Docs

Apollo Client helps you handle these errors according to their type, enabling you to show appropriate information to the user when an error...

Fix internet connection problems on Android devices

If you can't access the Internet on your Android device, either through an app or a website, try these troubleshooting steps. Signs of...

Troubleshoot Dataflow errors - Google Cloud

If you run into problems with your Dataflow pipeline or job, this page lists error messages that you might see and provides suggestions...

Troubleshooting Common Errors - Gatsby

Error : ReferenceError: window is not defined when running gatsby build · Build problems from Field 'browser' doesn't contain a valid alias configuration...