Marat Al
Marat Al
>where the API to generate this token is different of each type Correct. All those tokens come from different iOS frameworks. >might be quite difficult at the backend Agree, what...
At least it's what Apple says [here](https://developer.apple.com/documentation/corelocation/creating_a_location_push_service_extension#3875733) @Peter-Kubik
@stmoreau @lawrence-forooghian WDYT of adding just one additional token for simplicity?
@Peter-Kubik Some more information on how to handle device tokens here: https://developer.apple.com/documentation/pushkit/supporting_pushkit_notifications_in_your_app#3377584 >Because users can run your app on multiple devices, be prepared to handle multiple tokens for each notification...
Would you be able to read this dictionary? Where "deviceToken" is an old token, and "deviceTokens" (plural) - is the new one? You just read it like `recipient["deviceTokens"]["location"]`. Or it's...
>Would deviceTokens.default be the same as deviceToken Yes, but as I've mentioned above, not in the same request.
Yeah, it's less confusing this way, will do.
https://github.com/ably/ably-cocoa/issues/1305 @ikurek
https://github.com/ably/ably-cocoa/pull/1307
`ARTConnectionProtocol.maxMessageSize` is undocumented.