Subscription error - start received before the connection is initialised

[sokolej79]

Error 'start received before the connection is initialised' happens when websocket is connecting, but not yet conected and internet turned on. Use case: -turn off internet, websocket error not connected is raised after inactivityTimeout seconds in SocketClientConfig (default 30 seconds) -error happen only if inactivityTimeout is reached and socket disconnected -turn internet on again and subscribe to subscriptions, it will throw error: start received before the connection is initialised -subscriptions will not reconnect after this error

[thomas-ferchau]

We see this problem on the initial connection as well: #934

[vincenzopalazzo]

I will be on this issue and try to reproduce it, we are not happy with issues like this that are not able to reproduce the problem, but in this case, is our fault that we have no integration testing.

So, this can take a little bit because I'm building the integration architecture, if you want see the status it is available here https://github.com/vincenzopalazzo/keep-safe-graphql