Error: WebSocket is already in CLOSING or CLOSED state

After switching from subscriptions-transport-ws in Apollo client, there is always error WebSocket is already in CLOSING or CLOSED state after initialization in browser console.

Further Information

• graphql-ws: 5.6.2
• @apollo/client: 3.5.10
• Chrome: 99.0.4844.51

const wsLink = new GraphQLWsLink(
	createClient({
		url: 'ws://localhost:4000',
		connectionParams: async () => ({
			credentials: 'include',
			authorization: await getAuthToken(),
		}),
	})
)

[Mangatt]

Thanks, 5.6.3 have solved the problem.

[enisdenjo]

Inspecting the callstack and taking a hint from your further comment - I suspect that the connectionParams is taking too long to resolve, causing the server to kick off the client respecting the connectionInitWaitTimeout.

To solve it, simply increase the timeout on the server or speed up the connectionParams.

The fix released in v5.6.3 stops execution after connectionParams if the connection was closed while waiting. Previously, the client was trying to send a message afterwards regardless, leading to the error in the browser’s console.