@nilan @sorenbs I have tested again

subscriptions-transport-ws@0.7.1

this morning. While there is no longer a 400 error message, the server is sending a message of type “keepalive”, which is not exactly what the client expects. Instead, it expects “ka” for KEEP_ALIVE messages type. Because of this, the next error I see in the console is:

Uncaught Error: Invalid message type!
    at SubscriptionClient.processReceivedData (client.js:387)
    at WebSocket.client.onmessage (client.js:329)