Repository navigation
Conversation
davidliu
requested review from
MaxHeimbrock and
xianshijing-lk
as code owners
October 21, 2026 13:51
Contributor
|
Diffuse output: Base AAR cache miss. Please run the build job on main to generate the base AAR. |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
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
1 participant
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.29.2
Patch Changes
Keep dynacast-paused simulcast layers paused across publisher renegotiations. Previously a paused layer started to upload again after any renegotiation of the publisher connection. Publishing a track, unpublishing one, a codec change, and an ICE restart all caused this. With servers before v1.13.8, the layer stayed on until the next subscribed-quality change. Newer servers restate the pause a few seconds after the answer (dynacast: re-send subscribed qualities after every publisher answer livekit#4907), so there it stayed on for that window. - #1037 (@lukasIO)
The server's answer to a publisher offer no longer carries the RFC 8853 pause markers. Applying that answer re-enables every layer the client paused. Directly after it applies a publisher answer, the SDK now re-applies the last known subscribed codecs.
One frame per layer can still escape, because the encoders restart during the apply. This matches the JavaScript and Rust SDKs.