1.8.0

Full Changelog

What's Changed

• Introduce the new path-based LiveObjects API #1214. LiveObjects data is now accessed through channel.object, which returns a RealtimeObject exposing PathObjects — stable references to locations within the channel object that resolve to values dynamically at runtime, instead of explicit LiveMap/LiveCounter instances. See the PathObject documentation for details.

Breaking changes

This release replaces the previous experimental instance-based LiveObjects API with the new path-based API:

• The channel.getObjects() accessor (returning RealtimeObjects) has been replaced by the channel.object field (returning RealtimeObject)
• The io.ably.lib.objects package has been renamed to io.ably.lib.liveobjects
• Instead of obtaining and operating on explicit LiveMap/LiveCounter instances, data is accessed and mutated through PathObject references

1.7.2

What's Changed

• Fix preferred host persistence in HttpScheduler retry logic #1206

1.7.1

What's Changed

• Use server-provided GC grace period for LiveObjects garbage collection #1158
• Fix channel state updating before connection state listeners are notified (RTL3d1) #1202

1.7.0

What's Changed

• Introduce version 6 of the Ably protocol; add operation-specific payload fields to ObjectOperation and typed value fields to ObjectData #1195
• Add support for partial sync of LiveObjects state #1197
• Introduce ACK-based local application of LiveObjects ops #1194
• Add support for server-initiated MAP_CLEAR object operation #1198

1.6.1

What's Changed

• Upgrade msgpack-core to 0.9.11 to address security vulnerability #1188

1.6.0

What's Changed

• Message Updates and Deletes updated, Appends API added in #1182
• Mutable Message API over Realtime added in #1183
• Updated publish API to include message serials in the response in #1184

1.5.0

What's Changed

• Message Updates and Deletes API have been added in #1179
• The default http client has been changed to OkHttp in #1180

1.4.2

• Fixed an issue where async requests were not working after the realtime client reconnected following a manual close in #1176

1.4.1

What's Changed

• Fixed an error in the log when data field in Message is null in #1168
• Fixed an issue where presence would not send enter messages when the channel re-attaches after a disconnection in #1171
• AddedtoString method in ChannelStateChange class for improved debugging in #1169
• Fixed orphan Timer instances on release in #1173

1.4.0

What's Changed

• Protocol v4 support for enhanced message annotations and versioning #1163
• Support for clipped client ID lists and enhanced aggregation handling #1164
• Improved WebSocket transport lifecycle and activity management #1165