Ably Java client Library SDK release 1.1.6

Fixed bugs:

  • Unexpected exception in WsClient causing connection errors
  • bad rsv 4 error from WebsocketClient if transport is forced to close during handshake
  • fromCipherKey does not match spec

See GitHub for a full list of changes.

Ably .NET client library SDK release 1.1.15 beta1

v1.1.15 of Ably's .NET client library SDK has seen a significant rewrite of the library internals, which was needed to make the library safer and provide a good basis for implementing the rest of the spec.

Significant changes

  1. [Breaking] Presence and IRealtimeChannel no longer implement the IDisposable interface. They don't hold on to any unmanaged recourses and there was no need to expose the Dispose function.
  2. [Breaking] ITransport has acquired an Id Property and ITransportListener.OnTransportEvent has an Id parameter. This is needed because we need to distinguish events raised different Transport instances. Sometimes the Closed event doesn't get processed until another transport has already been instantiated.
  3. ClientOptions.CaptureCurrentSynchronizationContext has been deprecated and defaulted to false. It will be removed in future versions. You need to make sure that you don't directly update UI elements if you are building a WPF or Xamarin.Forms application from Ably handlers. If you still require the functionality please set it back to true and open an Ably Support ticket that you need the functionality. The main reason to disable this feature is that the library should not assume on which thread updates should be posted and that needs to be handled by the developer.
  4. IRealtimeClient implements IDisposable - If you want to clean up after the library you can now safely call Dispose(). Please note that you can no longer use this instance and have to create a new one.
  5. Logging has been greatly improved. We've removed a lot of verbose messages that brought little value. There is a helpful debug method called .GetCurrentState() on the realtime client that will dump the whole library's state as a json string. This will be helpful to include in the support tickets.

See GitHub for a full list of changes.

Ably Java client library SDK release 1.1.5

This is a bugfix release. Fixes:

  • WebSocketTransport: don't null the wsConnection in onClose()

See GitHub for a full list of changes.

Ably Java client library SDK release 1.1.4

This is a bugfix release.

  • Fixes an issue where state changes could cause an issue in the connection manager.

See GitHub for a full list of changes.

Ably .NET client library SDK release 1.1.14

Implemented enhancements to SDK:

  • TM3 Improvements

Fixed bugs:

  • Token Expiry error when QueryTime is set to true

Closed issues:

  • IO.Ably.AblyAuth RequestTokenAsync timeout exception not catchable

For full release notes, visit GitHub.

Previous releases on GitHub

Ably PHP client library SDK release 1.1.3

Adds support for extras in publish.

See GitHub for full release notes.

Ably Cocoa client library SDK release 1.1.12

Changes

  • Push: replace token NSData.description usage

Versions

Podfile

pod 'Ably', '1.1.12'

Cartfile

github "ably/ably-cocoa" == 1.1.12

Objective-C

#import <Ably/Ably.h>

Swift

import Ably

Compatibility

  • Carthage release for Swift is built with Xcode 11.1.

See GitHub for full release notes.

Previous releases on GitHub

Ably .NET client library SDK release 1.1.11

This is a bugfix release that reverts to protocol version to 1.0 to resolve issues with channel presence re-entry until a fix for the 1.1 protocol can be implemented.

Please see GitHub for more info.

Ably Java client library SDK release 1.1.3

This is a bugfix release.

Important changes

  • Fixed an issue relating to deleting locally persisted state when deregistering
  • Async callback fix

Complete list of changes available on GitHub.

Ably Cocoa library release 1.1.9

This is a bugfix release.

Important changes

Fixed bugs:

  • Push deactivate on an app is failing with push-subscribe permissions

Merged pull requests:

  • Delete device registration should not use the general-purpose endpoint

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.

  • 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

See full release notes on GitHub.