-
Notifications
You must be signed in to change notification settings - Fork 34
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
Leaving channel causes timeout #86
Comments
are you removing the channel from the socket as well? channel.leave()
socket.remove(channel) |
Yes, I also remove the channel. |
@dsrees Is there an update on this Since we are also facing this issue?? |
There is not. If you have time and want to investigate and submit a PR, I will gladly review it |
@dsrees If there is no activity on the fragment/activity , channels gets close(not sure why) which in turn closes the socket, then socket gets open again by the phoenix client, but why does it gets close every time after some n secs, also is there a way to increase this time limit. Thanks a lot. |
When leaving a channel I receive immediately the events:
However, channel.onClose() is triggered 10 seconds later due to timeout. This happens everytime.
The text was updated successfully, but these errors were encountered: