Skip to content

onBufferedAmountChange is not firing #214

Closed

Description

@zibet27

Describe the bug
onBufferedAmountChange never fires on macOS; other datachannel events work fine.

To Reproduce
Provided example uses Kotlin:

val nativeChannel: RTCDataChannel = pc.createDataChannel(label, RTCDataChannelInit())
nativeChannel.registerObserver(object : RTCDataChannelObserver {
            override fun onBufferedAmountChange(previousAmount: Long) {   
                 println("onBufferedAmountChange: $previousAmount")
            }
}

val largeData: ByteBuffer = createBytes(100 * 1024)
dataChannel1.send(RTCDataChannelBuffer(data, true))

// Nothing happens; the time limit is 5 seconds.

Expected behavior
The onBufferedAmountChange event should be fired once.

Desktop:

  • OS: macOS
  • Version: Sequoia

Activity

  1. devopvoid commented on Oct 19, 2025

    @devopvoid
    Owner

    Hi @zibet27, thanks for the report. I have to check this on my mac mini and will report back.

  2. zibet27 commented on Nov 12, 2025

    @zibet27
    Author

    Hi! @devopvoid, did you have a chance to check the issue?

  3. rnett commented on Dec 10, 2025

    @rnett

    @devopvoid I'm getting blocked by this as well, have you had a chance to look into it?

  4. zibet27 commented on Dec 19, 2025

    @zibet27
    Author

    @devopvoid The issue is actually already fixed by #206. I thought this commit was already published. I created a local Maven publication of the main branch, and it works as expected.
    When do you plan to release the next version?
    Sorry for the misunderstanding.

  5. ApoloApps commented on Jan 14, 2026

    @ApoloApps

    @devopvoid we too are blocked. A release would be appreciated!!!! :)

  6. rnett commented on Feb 19, 2026

    @rnett

    @devopvoid gentle bump

  7. devopvoid commented on Sep 13, 2026

    @devopvoid
    Owner

    Confirmed fixed by #206 (merged 2025-08-29), which added the missing OnBufferedAmountChange bridge in RTCDataChannelObserver. As @zibet27 found, that landed after v0.14.0 but the fix has been in every release since v0.15.0 (2026-08-16), and we're now on v0.17.0. Sorry for the long wait on a release — closing this out since it's shipped. If anyone's still seeing it not fire on a current release version, please reopen with your exact version.

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

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions