Marat Al
Marat Al
Reopened due to `ARTPresenceMessage` decoding implementation needed.
> If there are still types that we know need to be added, we should do this before doing a release. https://github.com/ably/ably-cocoa/pull/1973
@umair-ably couldn't you post here screenshots of the warnings/errors with `ARTRealtimeChannelOptions` and `ARTChannelProperties` you've mentioned in [this](https://github.com/ably/ably-cocoa/pull/1973) PR? I've also faced an error with the `properties` member in `final class...
> If you believe that this fixes the customer's crash (which it sounds like is urgent for them), then we can merge it and do a release. But I believe...
> > I don't think it should be reverted though, but rather be applied on top because error parser method will be unchanged or even extended > > Why would...
> I'm confused; why would we try and pick values out of any random API response that somebody might throw at us? It seems to me that trying to handle...
@lawrence-forooghian fixed
Turned out `detach` call fails with timeout if called during brief disconnection regardless `ATTACH` message sent after it. It only works if the channel successfully re-attaches first.
This is with logging on websocket level. After the message was sent nothing is received until timeout. Looks like realtime wants `ATTACH` message first. @owenpearson @lmars
>if you create a realtime connection and just send a DETACH for a random channel without attaching first, realtime still responds with a DETACHED If I call `detach` without attaching...