-
Notifications
You must be signed in to change notification settings - Fork 27.2k
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
Unable to find native implementation, or alternative implementation for WebSocket! #2604
Comments
Most likely on SSR I guess? |
Yes, But as per my understanding all the configurations will combine to make a Higher Order Component which renders on client side? |
@ads1018 any ideas 🤔 |
Hey @saadbinsaeed. @detrohutt managed to get subscriptions working with the next-apollo example. Here's the gist he shared of the changes he made to support subscriptions. Hope this helps. https://gist.github.com/detrohutt/3bddfe943a2f3ef2a797a6f7870049e8 |
Looks like you're enabling subscriptions on the server. You want to make sure to only enable on the client. |
Thanks @ads1018 ❤️ |
I have extended the with-apollo-redux example of next and using
subscriptions-transport-ws
for the web sockets. But sockets are not working and getting this errorThis is my
initApollo.js
Your Environment
The text was updated successfully, but these errors were encountered: