Skip to content

v2.31.0 - #1059

Open
davidliu wants to merge 1 commit into
mainfrom
changeset-release/main
Open

v2.31.0#1059
davidliu wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@davidliu

@davidliu davidliu commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

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

  • 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 (@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 (@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 (fix: expose participantIdentity on RoomEvent.DataReceived 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 (@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 RpcError messages to 256 bytes and data to 15 KB. - #1044 (@xianshijing-lk)

  • performRpc now 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 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 (fix(rpc): reject pending performRpc calls when the room disconnects 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 (@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)

@github-actions

github-actions Bot commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

Diffuse output:

Base AAR cache miss. Please run the build job on main to generate the base AAR.

@devin-ai-integration devin-ai-integration Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note

Newer findings are available below. Devin Review posted a newer report on this PR, in addition to the findings presented here.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 3 times, most recently from 07975cd to 52246a0 Compare November 9, 2026 21:08
@ve3344

ve3344 commented Nov 12, 2026

Copy link
Copy Markdown

@xianshijing-lk Could you please review this release? Thanks.

@davidliu davidliu changed the title v2.30.1 v2.31.0 Nov 13, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 52246a0 to 019ef63 Compare November 13, 2026 17:24
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 019ef63 to 74bb699 Compare November 14, 2026 04:31

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants