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.

Sign up for GitHub

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

Jump to bottom

Channels stay attached even if connection can't be resumed #105

Closed
SimonWoolf opened this issue Aug 26, 2015 · 1 comment
Closed

Channels stay attached even if connection can't be resumed #105

SimonWoolf opened this issue Aug 26, 2015 · 1 comment
Labels
bug Something isn't working. It's clear that this does need to be fixed.

Comments

@SimonWoolf
Copy link
Member

http://docs.ably.io/realtime/connection/ (under 'disconnected') says: "If connection state recovery is not possible following a new connection being established, all channels are detached".

This currently doesn't happen. On reconnect, even if realtime emits {"action":4,"error":{"message":"Invalid connection key specified to recover/resume","code":80008,"statusCode":400},"connectionId":"cEWCuTzuPp","connectionKey":"cEWCuTzuPpYvGVKN","connectionSerial":-1}, channels stay in the 'attached' state.
`
@SimonWoolf SimonWoolf added the bug Something isn't working. It's clear that this does need to be fixed. label Aug 26, 2015
@SimonWoolf SimonWoolf mentioned this issue Aug 26, 2015
Closed
@SimonWoolf
Copy link
Member Author

Fixed by #109

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working. It's clear that this does need to be fixed.
Milestone
No milestone
Development

No branches or pull requests
1 participant
@SimonWoolf