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.

v1.1.8

Important changes

Fixed bugs:

• Push deactivate/activate sequence results in stopped notifications #863
• Library apparently interpreting the connectionStateTtl with incorrect units #866

Merged pull requests:

• Push Device Update Registration: fix request authentication #867 (ricardopereira)
• Fix consecutive Authorizations #833 (ricardopereira)
• Fix milliseconds conversions #869 (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.8'

Cartfile

github "ably/ably-cocoa" == 1.1.8

Objective-C

#import <Ably/Ably.h>

Swift

import Ably

Compatibility

• Carthage release for Swift is built with Xcode 10.2.1.

v1.1.7

Important changes

Fixed bugs:

• Push deactivate/activate sequence results in stopped notifications #863

Merged pull requests:

• Fix Push Activation State Machine: WaitingForRegistrationUpdate bad state #864 (ricardopereira)

Complete list of changes available here.

Podfile

pod 'Ably', '1.1.7'

Cartfile

github "ably/ably-cocoa" == 1.1.7

Objective-C

#import <Ably/Ably.h>

Swift

import Ably

v1.1.6

Important changes

Fixed bugs:

• Lexical or Preprocessor Issue: 'SRWebSocket.h' file not found #840
• KSCrashAblyFork ksthread_getQueueName #846

Complete list of changes available here.

⚠️ Breaking changes

We changed the name of our SocketRocket framework to SocketRocketAblyFork. In case you're using the library with Carthage, then you need to update the path of the SocketRocket framework on your application targets’ Build Phases settings tab:

Podfile

pod 'Ably', '1.1.6'

Cartfile

github "ably/ably-cocoa" == 1.1.6

Objective-C

#import <Ably/Ably.h>

Swift

import Ably

v1.1.5

Important changes

Implemented enhancements:

• Swift 5 / Xcode 10.2 #838

Fixed bugs:

• Issue reported in iOS push tutorial #850

Complete list of changes available here.

Podfile

pod 'Ably', '1.1.5'

Cartfile

github "ably/ably-cocoa" == 1.1.5

Objective-C

#import <Ably/Ably.h>

Swift

import Ably

v1.1.4

Important changes

Implemented enhancements:

• Add idempotent REST publishing #749

Fixed bugs:

• Default token params should not include a capabilities member #576
• Unsubscribe on channel enumeration causing crash #842

Complete list of changes available here.

Podfile

pod 'Ably', '1.1.4'

Cartfile

github "ably/ably-cocoa" == 1.1.4

Objective-C

#import <Ably/Ably.h>

Swift

import Ably

v1.1.3

Important changes include:

• macOS Support
• tvOS Support

Complete list of changes available here.

Podfile

pod 'Ably', '1.1.3'

Cartfile

github "ably/ably-cocoa" == 1.1.3

Objective-C

#import <Ably/Ably.h>

Swift

import Ably

v1.1.2

Important changes include:

• Update to Xcode 10 (Swift 4.2) #813
• HTTP Paginated Response implemented #783
• Unable to submit to AppStore has been fixed #803

Complete list of changes available here.

Podfile

pod 'Ably', '1.1.2'

Cartfile

github "ably/ably-ios" == 1.1.2

Objective-C

#import <Ably/Ably.h>

Swift

import Ably