graphql-ws: [ReactNative] Slow refresh subscription causes websocket close with {"isTrusted": false, "message": null}

Screenshot Visualising is always helpful.

Working subscription. This one doesn’t authenticate in the backend and seems to work fine.

Wheras one that does authenticate:

As you can see causes ERROR {"isTrusted": false, "message": null} issue. However, the initial graphql subsciption was successful. Giving me back Authenticated data! It’s only the new ones that fail.

Expected Behaviour I expected it to work in react-native. Since my code seems to work quite well in a regular environment,

Actual Behaviour but instead it did ERROR {"isTrusted": false, "message": null}

Debug Information I don’t see any error logs on my backend. Everything seems A OK back there. The only other difference between the two subscriptions in the backend are that the “Hello” one responds every second. While the heartBeat takes 10 seconds.

Further Information I recreated my scenario on a Sandbox that supports react-native. Of course this isn’t the exact environmment. But it works great!

I use expo to compile to Android. Not doing anything too fancy outside the codesandbox example.