Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Subscriptions fails with untraceable error #37

Closed
gpsamson opened this issue Jan 23, 2017 · 1 comment
Closed

Subscriptions fails with untraceable error #37

gpsamson opened this issue Jan 23, 2017 · 1 comment

Comments

@gpsamson
Copy link

gpsamson commented Jan 23, 2017

I've been trying to trace a subscription_failed error for hours without any success. The data sent to the client on failure is {"type":"subscription_fail","id":0,"payload":{"errors":[{"message":"Cannot read property 'forEach' of undefined"}]}}.

There is nothing logged to the console of the server. I've also checked the application code and there is no use of forEach so I suspect it's rooted in graphql-subscriptions or subscriptions-transport-ws. Both the client and server are using the latest releases of the Apollo stack.

Subscriptions were working flawlessly up until I resumed development today. I'm going to check out the master branch and see if it the error is still happening. I'll also attempt a clean install.

I couldn't find an issue similar to this one so I'm opening this in hope of some direction. Any help is much appreciated.

@gpsamson
Copy link
Author

Fixed - An incorrect GQL query on the client side was making the subscription manager throw this vague error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant