Marat Al

This should be solved with an issue for every test.

Related issue https://github.com/ably/ably-cocoa/issues/1914

> > I’m setting this as a medium priority but it’s a bit of a guess — I don't know how often the described scenario occurs in reality. > >...

> It seems like something we should implement; why would we close it? Sorry, I've meant the PR, not clear to me what to do with it now. Shouldn't be...

see https://github.com/ably/ably-cocoa/issues/1848

Because this will replace core/critical functionality, it is probably a good idea to introduce it gradually via something like `clientOptions.useNativeWebSocket` and explicitly ask some clients to give it a try....

> I noticed that the `Network` framework provides WebSocket functionality through [`NWProtocolWebSocket`](https://developer.apple.com/documentation/network/nwprotocolwebsocket), also introduced in iOS 13; do you know if/how this differs to `NSURLSessionWebSocketTask`? [Looks](https://developer.apple.com/documentation/network/nwprotocolwebsocket) like it's swift only....

> Ah, OK. There is also a C version, though. [Apple’s guidance](https://developer.apple.com/documentation/technotes/tn3151-choosing-the-right-networking-api#WebSocket) is to favour the Network framework: > > > Unless you have a specific reason to use URLSession,...

https://ably.com/docs/api/rest-api#post-device-registration ``` curl -X POST https://rest.ably.io/push/deviceRegistrations \ -u "******" -H "Content-Type: application/json" \ --data \ '{ "id": "*****", "platform": "ios", "formFactor": "phone", "push": { "recipient": { "transportType": "apns", "deviceToken": "***"...

I've meant having keys for different platforms in one dictionary is probably not the best recipe to handle on the server, but someone from a server side team can have...