You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since incorporating graphql-modules I've not been able to get a subscription socket to connect and stay connected. The socket sends a connection_init message and then dies.
I've not been able to find any examples or documentation on using this library with Apollo's latest subscription recommendations, which is to create a SubscriptionServer directly.
To Reproduce
Here's how I'm setting up the server. I'll try to find some time to create a sandbox for reproduction.
Apologies for my misunderstanding here, we tried rolling back the inclusion of this library and found similar problems existed. I do think some more documentation on usage with subscriptions and modern Apollo would be nice, but the problem itself seems to lie elsewhere. Feel free to close.
Describe the bug
Since incorporating
graphql-modules
I've not been able to get a subscription socket to connect and stay connected. The socket sends a connection_init message and then dies.I've not been able to find any examples or documentation on using this library with Apollo's latest subscription recommendations, which is to create a
SubscriptionServer
directly.To Reproduce
Here's how I'm setting up the server. I'll try to find some time to create a sandbox for reproduction.
Expected behavior
I expect the Subscription client to connect via websocket and receive an ack, then maintain the connection.
I also expect the console logs to be invoked from my SubscriptionServer (they're not)
Environment:
@graphql-modules/1.4.4
:Additional context
The Apollo subscriptions example seems to use an API that's no longer part of their documentation in either v2 or v3.
The text was updated successfully, but these errors were encountered: