Skip to content
Discussion options

You must be logged in to vote

Are you sure you're using graphql-ws on both sides (client and server)? Note that graphql-ws is not backwards compatible with the legacy subscriptions-transport-ws protocol.

Furthermore, there is no error with just the message Invalid message anywhere in graphql-ws codebase (see here).

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by enisdenjo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #451 on February 28, 2023 08:46.