Reconnection not working on Chrome

[Emilios1995]

Screenshot

Expected Behaviour
Disconnecting the client from the internet and the reconnecting should cause it to reconnect when graphql-sse performs a re-connection attempt.

I'm using a mostly standard setup of the graphql-sse client with Relay.

Actual Behaviour
I see an error ending up in the console as in the screenshot. It's not being handled by graphql-sse and reconnecting. The error ends up at the top of my sink.

Firefox and Edge actually work for me. The problem is in Chrome and Safari.

Debug Information
I discovered that the error surfaces in this catch clause in the form of a TypeError with the message: network error (which is standard with the Fetch API AFAIK) but since it was never converted to a NetworkError, it doesn't trigger a retry.

I dug deeper to find the source of the error and see why it wasn't converted to NetworkError and noticed that it was thrown from the toAsyncIterator function, from which apparently you didn't anticipate network errors occurring.

Further Information

• I tried disabling the QUIQ protocol via a Chrome flag and the console error changes to ERR_NETWORK_CHANGED

Pleas let me know if you aren't able to reproduce and whether I can help with anything.

[enisdenjo]

Great catch! I've noticed it also with #22 (comment) but you beat me to creating an issue.

Thanks for reporting! I'll take care of it soon. 👍

[enisdenjo]

🎉 This issue has been resolved in version 1.2.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[enisdenjo]

Seems like this issue is still present in Safari and Firefox.

• Safari because when the server terminates, the connection completes (does not error out) (see Network errors during event emission not retried in Safari #28)
• Firefox because the error message does not contain the keyword "network"

[enisdenjo]

Firefox is now handled with 054f16b and released in v1.2.2.