Invalid message Error in subscription #452
-
Expected Behaviour It should not throw error and subscribe to data Actual Behaviour It throws Debug Information The subscription configuration seems fine and connection get successfull initially. Further Information I'm using NestJS v |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
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 |
Beta Was this translation helpful? Give feedback.
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).