Ably's changelog www.ably.com

New feature

Using inband channel occupancy events, Ably users can subscribe to occupancy metadata events relating to a single channel. These events are then delivered to the client as messages on the channel itself. 

This feature allows developers to understand the exact numbers of connections, publishers, subscribers, presence connections, presence members, and presence subscribers relating to a channel. This information can be used for debugging and monitoring purposes, or for business logic - such as publishing a certain announcement on the channel only when you reach a certain number of subscribers.  

How does it work?

Inband channel occupancy events are added in addition to existing occupancy metachannel and Channel Status API, and provides a convenient interface to work with Occupancy in a streaming manner and within the scope of a single channel. Read more about inband channel occupancy in our documentation.

How do I get started with Inband channel occupancy events?

Take a look at this step-by-step tutorial to learn how to subscribe to inband channel occupancy events.

How do I give feedback on this feature?

We rely on your feedback to improve this feature; please either raise issues or pull requests. You can also contact us at any time if you would like to talk about contributing or feature requests.

Client Library SDK Fix

Fixed bugs:

• Specify channel modes to limit the amount of unnecessary data being sent and received over Ably #412
• EnhancedLocationUpdate timestamps do not represent real world time #387

Early access

Client Library SDK Improvement

Ably Flutter v1.2.2 is now available for preview, adding support for push notifications, including device activation with Ably (including device registration with APNs / FCM) and subscribing devices for push notifications. Check out the dedicated documentation and the example app for more information.

Full Changelog

Implemented enhancements:

• Push Notifications Device Registration (activation) and device subscription #107

Merged pull requests:

• Add documentation for token authentication #155 (ben-xD)
• Push notifications (activation and subscription) #140 (ben-xD)

Client Library SDK Fix

Implemented enhancements:

• Update Stats fields with latest MessageTraffic types #394
• Replace ULID with Android's UUID #680

Fixed bugs:

• Push Activation State Machine exception handling needs improvement #685
• WebsocketNotConnectedException on send #430

Client Library SDK Fix

Fixed bugs

• Implement RTL5b and RTL5j cases for detaching from channels in suspended/failed states #784

Client Library SDK Improvement

Implemented enhancements

• Add .once method to EventEmitter #779
• Implement Ably-Agent connection param for ably-js and NodeJS versions #740

Fixed bugs

• Fix channel names as object prototype keys #777
• Bump ws from 5.2.2 to 5.2.3 #781

New feature

Control API gives you an easy way to configure Ably programmatically. It is a REST API that can be used to create, configure and delete the following Ably resources:

• Apps
• API keys
• Channel rules/Namespaces
• Queues
• Rules
• Stats (not available in beta)

Control API is useful when you need to create a testing or acceptance environment that is identical to production. You can provision and tear down Ably apps through the Control API with one script that runs multiple times. Or, you can track and synchronize changes to production from config management tools such as Terraform or CloudFormation via Control API .

To access Control API, log into your Ably dashboard, go to 'My Access Tokens' in the top menu bar, then create an access token. Specify the capabilities and rights for your access tokens, then create them. You can revoke or edit tokens at any time.

For more information, check out the docs. You can also test out requests, see responses, and test your client app against a mock server. And you can always get in touch with our experts.

Client Library SDK Improvement

• Improved background notifications
• Sends trip start and end events on new meta channel
• Kotlin 1.5.0 and new JVM IR backend
• Enhancements to example apps
• Bug fixes

Full Details

Client Library SDK Fix

Fixed bugs:

• Bind setImmediate to global object in browsers #774

Client Library SDK Improvement

For this release, we focused mainly on improving the Realtime component of the SDK. The previous release only supported the currently depreciated version 0.8 of the Ably Client Library Specification, but this version supports the latest version of the specification.

Since the functionality of the realtime library has significantly expanded during the transition from version 0.8 to 1.2, the changes have affected almost all components of the library including:

• RealTime Client

• Connection management and error handling

• Channel management

The REST API has also been aligned with version 1.2 of the Ably Client Library specification, including Authentication and Encryption capabilities.

Full release notes and changelog on GitHub.