Repository navigation
Conversation
davidliu
requested review from
MaxHeimbrock and
xianshijing-lk
as code owners
November 3, 2026 07:41
Contributor
|
Diffuse output: Base AAR cache miss. Please run the build job on main to generate the base AAR. |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
November 9, 2026 21:08
07975cd to
52246a0
Compare
|
@xianshijing-lk Could you please review this release? Thanks. |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 13, 2026 17:24
52246a0 to
019ef63
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 14, 2026 04:31
019ef63 to
74bb699
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
client-sdk-android@2.31.0
Minor Changes
ConnectOptions.singlePeerConnection, which joins through the/rtc/v1signal 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/v1answers 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 (@changt)Patch Changes
Expose
participantIdentityonRoomEvent.DataReceived. The event'sparticipantis 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:onUserPacketwas handed only the innerUserPacket, while the authoritative identity lives on the enclosingDataPacket. - #1046 (@xianshijing-lk)The internal engine listener now forwards that identity, and it is reported on every
DataReceivedevent whether or not the sender resolves to aRemoteParticipant.This matches the JavaScript SDK (fix: expose participantIdentity on RoomEvent.DataReceived client-sdk-js#2092).
Add proportional jitter to the default reconnect delays.
DefaultReconnectPolicyreturned 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 (@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 (fix: add proportional jitter to default reconnect delays client-sdk-js#2124).
Fix not truncating outgoing
RpcErrormessages to 256 bytes and data to 15 KB. - #1044 (@xianshijing-lk)performRpcnow fails as soon as the room disconnects, rather than staying suspended until its response timeout. - #1067 (@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
responseTimeoutafter the room had gone. The caller's coroutine is now resumed withRECIPIENT_DISCONNECTEDinstead.This matches the Rust SDK's
fail_all_pendingand the Swift SDK'shandleAllPendingDisconnected(fix(rpc): reject pending performRpc calls when the room disconnects client-sdk-js#2251).Move RTCEngine's peer connections behind an internal
Transportinterface.DualPeerConnectionTransportimplements 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 (@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 (@xianshijing-lk)