-
-
Notifications
You must be signed in to change notification settings - Fork 81
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
Error when connected to socket #23
Comments
I know this issue, I'm going to fix it ASAP :) Also, always welcome to PR. |
Hello @cesarmtaz, |
Hey @meAbhishekTripathi, |
<addr.>
|
@WrathChaos Did you found the solution for that, I am facing the same issue. It's working fine with android and web but in iOS after connection establishment it got disconnected . |
Hello @amit3215 and @anhdaden12,
If the problem stands still please open a new issue :) |
@amit3215 on ios platform i solve this problem by send a ping to socket server per 10s. I just send "\n" and it solved my case, like picture below |
Hi,
im getting this error didCloseWithCode 1000, reason: Optional(""Session closed by the container because of the idle timeout."") or didCloseWithCode 1001, reason: Optional("Stream end encountered")
it gets connected but when I subscribe y get this errors this is my channel "/wsc/info/user/"
The text was updated successfully, but these errors were encountered: