Releases: ably/ably-cocoa
v1.1.15
Important changes
Complete list of changes available here.
⚠️ Breaking changes
We changed the name of our version of KSCrash
framework to KSCrashAblyFork
. In case you're using the library with Carthage, then you need to update the name of the KSCrash
framework on your application targets’ Build Phases settings tab.
Versions
Podfile
pod 'Ably', '1.1.15'
Cartfile
github "ably/ably-cocoa" == 1.1.15
Objective-C
#import <Ably/Ably.h>
Swift
import Ably
Compatibility
- Carthage release for Swift is built with Xcode 11.3.
v1.1.15 - Beta 1
Changes
Continuation of the attempt to fix an issue experienced by those specifying the Ably pod as a dependency in their own CocoaPod spec, relating to the Ably fork of the KSCrash and MsgPack framework.
Partially addressing #949
Versions
Podfile
pod 'Ably', '1.1.15-beta.1'
Cartfile
WARNING This beta release has been created as an attempt to fix a CocoaPods related issue. As such there is a possibility that inclusion via Carthage may not work.
github "ably/ably-cocoa" == 1.1.15-beta.1
Objective-C
#import <Ably/Ably.h>
Swift
import Ably
v1.1.15 - Beta 0
Changes
This is an attempt to fix an issue experienced by those specifying the Ably pod as a dependency in their own CocoaPod spec, relating to the Ably fork of the KSCrash framework.
Partially addressing #949
Versions
Podfile
pod 'Ably', '1.1.15-beta.0'
Cartfile
WARNING This beta release has been created as an attempt to fix a CocoaPods related issue. As such there is a possibility that inclusion via Carthage may not work.
github "ably/ably-cocoa" == 1.1.15-beta.0
Objective-C
#import <Ably/Ably.h>
Swift
import Ably
v1.1.14
Changes
Bug fixes:
- iOS Incompatible library version crash - DYLIB_COMPATIBILITY_VERSION vs DYLIB_CURRENT_VERSION #946: We were publishing incorrect metadata in our dynamic library for iOS.
Versions
Podfile
pod 'Ably', '1.1.14'
Cartfile
github "ably/ably-cocoa" == 1.1.14
Objective-C
#import <Ably/Ably.h>
Swift
import Ably
Compatibility
- Carthage release for Swift is built with Xcode 11.2.1.
v1.1.13
Changes
Bug fixes:
- Using
clientId
no longer forces token auth, per 1.1. spec #849 - Network Reachability #908
- Multi-threaded stability improvements #918, #919, #920
- Possibility of out-of-order publishing #926
Versions
Podfile
pod 'Ably', '1.1.13'
Cartfile
github "ably/ably-cocoa" == 1.1.13
Objective-C
#import <Ably/Ably.h>
Swift
import Ably
Compatibility
- Carthage release for Swift is built with Xcode 11.1.
v1.1.12
v1.1.11 - Beta 1
Important changes
- Push: replace system
NSLog
with internalARTLogger
#896 - Push: replace token
NSData.description
usage #889 - Push: fix crash "dispatch_sync called on queue already owned by current thread" #888
- Push:
PushChannel.subscribe
should not call the callback in the internal queue #862
Tentative fix of:
- Crash on creating weak ref to deallocating object #879
Versions
Podfile
pod 'Ably', '1.1.11-beta.1'
Cartfile
github "ably/ably-cocoa" == 1.1.11-beta.1
Objective-C
#import <Ably/Ably.h>
Swift
import Ably
Compatibility
- Carthage release for Swift is built with Xcode 11.0.
v1.1.11 - Beta 0
Important changes
Tentative fix of:
- Crash on creating weak ref to deallocating object #879
Versions
Podfile
pod 'Ably', '1.1.11-beta.0'
Cartfile
github "ably/ably-cocoa" == 1.1.11-beta.0
Objective-C
#import <Ably/Ably.h>
Swift
import Ably
v1.1.10
Important changes
Fixed bugs:
- Push device registration omits
clientId
#877
Complete list of changes available here.
Versions
Podfile
pod 'Ably', '1.1.10'
Cartfile
github "ably/ably-cocoa" == 1.1.10
Objective-C
#import <Ably/Ably.h>
Swift
import Ably
Compatibility
- Carthage release for Swift is built with Xcode 10.2.1.
v1.1.9
Important changes
Fixed bugs:
- Push deactivate on an app is failing with
push-subscribe
permissions #873
Merged pull requests:
- Delete device registration should not use the general-purpose endpoint #871 (ricardopereira)
Complete list of changes available here.
⚠️ Important notes
Push related
Whenever a new device token occurs in application(_:didRegisterForRemoteNotificationsWithDeviceToken:)
, the library was updating the LocalDevice.deviceIdentityTokenDetails
with invalid data. The issue causing this was in the deviceUpdateRegistration:
method (#867).
After updating to this version, because of the bad state of deviceIdentityTokenDetails
, it is possible that a response error with status code 401 occurs when a PATCH /push/deviceRegistrations
request is done:
error = {
code = 40100;
href = "https://help.ably.io/error/40100";
message = "Incompatible deviceSecret specified for device access. (See https://help.ably.io/error/40100 for help.)";
serverId = "frontend.33f8.1.eu-central-1-A.i-00dc4bfbae5ebfeac";
statusCode = 401;
};
✅ The recommended way to fix the deviceIdentityTokenDetails
bad state is to deactivate() -> activate()
the device.
Versions
Podfile
pod 'Ably', '1.1.9'
Cartfile
github "ably/ably-cocoa" == 1.1.9
Objective-C
#import <Ably/Ably.h>
Swift
import Ably
Compatibility
- Carthage release for Swift is built with Xcode 10.2.1.