- `Attach` related changes were introduced as a part of protocol 2. - As per protocol 2, ATTACH msg should be sent for every channel in `attaching`, `attached` and `suspended` states once `connected`. - There are various mechanisms by which duplicate ATTACH will be sent 1. `ATTACH` is added to the connection or global queue before being sent, check description on -> https://github.com/ably/ably-ruby/pull/416 2. `ATTACH` is sent periodically when channel is in `SUSPENDED` state as per https://sdk.ably.com/builds/ably/specification/main/features/#RTL13b. Timers sending `ATTACH` periodically can cause duplicate `ATTACH` being sent on `CONNECTED` ┆Issue is synchronized with this [Jira Task](https://ably.atlassian.net/browse/ECO-4860) by [Unito](https://www.unito.io)
Attachrelated changes were introduced as a part of protocol 2.attaching,attachedandsuspendedstates onceconnected.ATTACHis added to the connection or global queue before being sent, check description on -> [ECO-4687][Protocol-2] Fix duplicate outgoing ATTACH msg ably-pubsub-ruby#416ATTACHis sent periodically when channel is inSUSPENDEDstate as per https://sdk.ably.com/builds/ably/specification/main/features/#RTL13b. Timers sendingATTACHperiodically can cause duplicateATTACHbeing sent onCONNECTED┆Issue is synchronized with this Jira Task by Unito