From 74bb69901917414da26daa6edf219aedccd6ffa9 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Sat, 14 Nov 2026 04:31:38 +0000 Subject: [PATCH] v2.31.0 --- .../data-received-participant-identity.md | 9 ------ .changeset/reconnect-delay-jitter.md | 9 ------ .changeset/rpc-error-truncate-on-send.md | 5 --- .../rpc-reject-pending-on-disconnect.md | 9 ------ .changeset/single-peer-connection.md | 5 --- .changeset/transport-interface.md | 5 --- .changeset/truncate-bytes-surrogate-pair.md | 5 --- CHANGELOG.md | 32 +++++++++++++++++++ README.md | 4 +-- gradle.properties | 2 +- package.json | 2 +- 11 files changed, 36 insertions(+), 51 deletions(-) delete mode 100644 .changeset/data-received-participant-identity.md delete mode 100644 .changeset/reconnect-delay-jitter.md delete mode 100644 .changeset/rpc-error-truncate-on-send.md delete mode 100644 .changeset/rpc-reject-pending-on-disconnect.md delete mode 100644 .changeset/single-peer-connection.md delete mode 100644 .changeset/transport-interface.md delete mode 100644 .changeset/truncate-bytes-surrogate-pair.md diff --git a/.changeset/data-received-participant-identity.md b/.changeset/data-received-participant-identity.md deleted file mode 100644 index f91cecf3e..000000000 --- a/.changeset/data-received-participant-identity.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -"client-sdk-android": patch ---- - -Expose `participantIdentity` on `RoomEvent.DataReceived`. The event's `participant` is nullable and is null whenever the sender is not in the room — data sent through the Server API, or by a participant that has already left. In that case the receiver had no way to tell who sent the data, because the engine dropped the identity before building the event: `onUserPacket` was handed only the inner `UserPacket`, while the authoritative identity lives on the enclosing `DataPacket`. - -The internal engine listener now forwards that identity, and it is reported on every `DataReceived` event whether or not the sender resolves to a `RemoteParticipant`. - -This matches the JavaScript SDK (livekit/client-sdk-js#2092). diff --git a/.changeset/reconnect-delay-jitter.md b/.changeset/reconnect-delay-jitter.md deleted file mode 100644 index cbc1ccf7d..000000000 --- a/.changeset/reconnect-delay-jitter.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -"client-sdk-android": patch ---- - -Add proportional jitter to the default reconnect delays. `DefaultReconnectPolicy` returned a fixed delay for each retry count, so every client disconnected by the same event — a server restart, a region failover, a dropped uplink — waited exactly 100ms, then 300ms, then 300ms, and so on, in lockstep. They retried as one herd and could keep re-synchronising across attempts. - -Each delay is now scaled by a random factor between 0.5 and 1.5, spreading clients further apart with every retry. A first retry whose configured delay is zero instead draws from a fixed 0–500ms window, since there is no base delay to scale; a zero at any later index still means retry immediately. - -This matches the JavaScript SDK (livekit/client-sdk-js#2124). diff --git a/.changeset/rpc-error-truncate-on-send.md b/.changeset/rpc-error-truncate-on-send.md deleted file mode 100644 index 9b7028b45..000000000 --- a/.changeset/rpc-error-truncate-on-send.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"client-sdk-android": patch ---- - -Fix not truncating outgoing `RpcError` messages to 256 bytes and data to 15 KB. diff --git a/.changeset/rpc-reject-pending-on-disconnect.md b/.changeset/rpc-reject-pending-on-disconnect.md deleted file mode 100644 index cb8ecedbf..000000000 --- a/.changeset/rpc-reject-pending-on-disconnect.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -"client-sdk-android": patch ---- - -`performRpc` now fails as soon as the room disconnects, rather than staying suspended until its response timeout. - -Room cleanup reports every remote participant as disconnected, which already rejected calls addressed to a participant the room knew about. A call to an identity that never appeared in the participant list — an agent that has not joined yet, say — was in no such loop, so it stayed pending for the full `responseTimeout` after the room had gone. The caller's coroutine is now resumed with `RECIPIENT_DISCONNECTED` instead. - -This matches the Rust SDK's `fail_all_pending` and the Swift SDK's `handleAllPendingDisconnected` (livekit/client-sdk-js#2251). diff --git a/.changeset/single-peer-connection.md b/.changeset/single-peer-connection.md deleted file mode 100644 index 0f030623a..000000000 --- a/.changeset/single-peer-connection.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"client-sdk-android": minor ---- - -Add `ConnectOptions.singlePeerConnection`, which joins through the `/rtc/v1` signal path and publishes and receives on one peer connection instead of a publisher and a subscriber. The client makes every offer; the server's media sections requirement adds receive-only transceivers, and the answer's mid-to-track mapping resolves received tracks. A server without `/rtc/v1` answers that handshake with 404, in which case the join retries on the legacy path with dual peer connections and later reconnects stay there. The option is off by default. diff --git a/.changeset/transport-interface.md b/.changeset/transport-interface.md deleted file mode 100644 index 81753e923..000000000 --- a/.changeset/transport-interface.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"client-sdk-android": patch ---- - -Move RTCEngine's peer connections behind an internal `Transport` interface. `DualPeerConnectionTransport` implements it for the existing publisher and subscriber peer connection pair and owns the decisions that depend on that arrangement: ICE candidate routing, answering server offers, which peer connections a resume waits on, and the sync state descriptions. No behavior changes. diff --git a/.changeset/truncate-bytes-surrogate-pair.md b/.changeset/truncate-bytes-surrogate-pair.md deleted file mode 100644 index 23d8ade94..000000000 --- a/.changeset/truncate-bytes-surrogate-pair.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"client-sdk-android": patch ---- - -Fix long RPC error messages and data sometimes ending in a garbled character when truncated in the middle of an emoji or similar character. diff --git a/CHANGELOG.md b/CHANGELOG.md index d8b70142e..b75162b74 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,37 @@ # client-sdk-android +## 2.31.0 + +### Minor Changes + +- Add `ConnectOptions.singlePeerConnection`, which joins through the `/rtc/v1` signal path and publishes and receives on one peer connection instead of a publisher and a subscriber. The client makes every offer; the server's media sections requirement adds receive-only transceivers, and the answer's mid-to-track mapping resolves received tracks. A server without `/rtc/v1` answers that handshake with 404, in which case the join retries on the legacy path with dual peer connections and later reconnects stay there. The option is off by default. - [#1066](https://github.com/livekit/client-sdk-android/pull/1066) ([@changt](https://github.com/changt)) + +### Patch Changes + +- Expose `participantIdentity` on `RoomEvent.DataReceived`. The event's `participant` is nullable and is null whenever the sender is not in the room — data sent through the Server API, or by a participant that has already left. In that case the receiver had no way to tell who sent the data, because the engine dropped the identity before building the event: `onUserPacket` was handed only the inner `UserPacket`, while the authoritative identity lives on the enclosing `DataPacket`. - [#1046](https://github.com/livekit/client-sdk-android/pull/1046) ([@xianshijing-lk](https://github.com/xianshijing-lk)) + + The internal engine listener now forwards that identity, and it is reported on every `DataReceived` event whether or not the sender resolves to a `RemoteParticipant`. + + This matches the JavaScript SDK (livekit/client-sdk-js#2092). + +- Add proportional jitter to the default reconnect delays. `DefaultReconnectPolicy` returned a fixed delay for each retry count, so every client disconnected by the same event — a server restart, a region failover, a dropped uplink — waited exactly 100ms, then 300ms, then 300ms, and so on, in lockstep. They retried as one herd and could keep re-synchronising across attempts. - [#1045](https://github.com/livekit/client-sdk-android/pull/1045) ([@xianshijing-lk](https://github.com/xianshijing-lk)) + + Each delay is now scaled by a random factor between 0.5 and 1.5, spreading clients further apart with every retry. A first retry whose configured delay is zero instead draws from a fixed 0–500ms window, since there is no base delay to scale; a zero at any later index still means retry immediately. + + This matches the JavaScript SDK (livekit/client-sdk-js#2124). + +- Fix not truncating outgoing `RpcError` messages to 256 bytes and data to 15 KB. - [#1044](https://github.com/livekit/client-sdk-android/pull/1044) ([@xianshijing-lk](https://github.com/xianshijing-lk)) + +- `performRpc` now fails as soon as the room disconnects, rather than staying suspended until its response timeout. - [#1067](https://github.com/livekit/client-sdk-android/pull/1067) ([@xianshijing-lk](https://github.com/xianshijing-lk)) + + Room cleanup reports every remote participant as disconnected, which already rejected calls addressed to a participant the room knew about. A call to an identity that never appeared in the participant list — an agent that has not joined yet, say — was in no such loop, so it stayed pending for the full `responseTimeout` after the room had gone. The caller's coroutine is now resumed with `RECIPIENT_DISCONNECTED` instead. + + This matches the Rust SDK's `fail_all_pending` and the Swift SDK's `handleAllPendingDisconnected` (livekit/client-sdk-js#2251). + +- Move RTCEngine's peer connections behind an internal `Transport` interface. `DualPeerConnectionTransport` implements it for the existing publisher and subscriber peer connection pair and owns the decisions that depend on that arrangement: ICE candidate routing, answering server offers, which peer connections a resume waits on, and the sync state descriptions. No behavior changes. - [#1064](https://github.com/livekit/client-sdk-android/pull/1064) ([@changt](https://github.com/changt)) + +- Fix long RPC error messages and data sometimes ending in a garbled character when truncated in the middle of an emoji or similar character. - [#1044](https://github.com/livekit/client-sdk-android/pull/1044) ([@xianshijing-lk](https://github.com/xianshijing-lk)) + ## 2.30.0 ### Minor Changes diff --git a/README.md b/README.md index 78fd23702..4cdffb9bf 100644 --- a/README.md +++ b/README.md @@ -84,7 +84,7 @@ LiveKit for Android is available as a Maven package. ```groovy title="build.gradle" ... dependencies { - def livekit_version = "2.30.0" + def livekit_version = "2.31.0" implementation "io.livekit:livekit-android:$livekit_version" @@ -95,7 +95,7 @@ dependencies { implementation "io.livekit:livekit-android-track-processors:$livekit_version" // Snapshots of the latest development version are available at: - // implementation "io.livekit:livekit-android:2.30.1-SNAPSHOT" + // implementation "io.livekit:livekit-android:2.31.1-SNAPSHOT" } ``` diff --git a/gradle.properties b/gradle.properties index 6ee510a65..e521f7fc1 100644 --- a/gradle.properties +++ b/gradle.properties @@ -33,7 +33,7 @@ kapt.use.worker.api=true ############################################################### GROUP=io.livekit -VERSION_NAME=2.30.0 +VERSION_NAME=2.31.0 POM_DESCRIPTION=LiveKit Android SDK, WebRTC Rooms diff --git a/package.json b/package.json index e39563ac6..0545de2b3 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "client-sdk-android", - "version": "2.30.0", + "version": "2.31.0", "repository": "https://github.com/livekit/client-sdk-android.git", "license": "Apache License 2.0", "private": true,