Headless Player: BufferedRanges event emitter/listener stops updating


1. Summary

When using headless playback, the bufferedRangesListener of the playerClient becomes very inconsistent in it’s reporting almost immediately, sometimes reporting in bursts, sometimes with long breaks between reports, and eventually stops responding all together.

Bug Severity

  • Impacts operation of app
  • Blocks current development
  • Improvement suggestion
  • Issue with documentation (If selected, please share the doc link and describe the issue)
  • Other

2. Steps to Reproduce

Start a headless playback sesison, and subscribe to the bufferedRangesListener of the player client

3. Observed Behavior

When using headless playback, the bufferedRangesListener of the playerClient becomes very inconsistent in it’s reporting almost immediately, sometimes reporting in bursts, sometimes with long breaks between reports, and eventually stops responding all together.

4. Expected Behavior

Describe what you expected the SDK to do under normal operation.

We would expect the buffered ranges to update appropriately when the range of the buffered media changes so we can calculate proper seek ranges in the media

4.a Possible Root Cause & Temporary Workaround

Fill out anything you have tried. If you don’t know, N/A is acceptable

<!-- Answer here -->

5. Logs or crash report

onPositionUpdated:  2174.092999
onPositionUpdated:  2174.092999
onPositionUpdated:  2174.092999
onBufferedRangesUpdated: [{"end":2177.818112,"start":2171.784067}]
onBufferedRangesUpdated: [{"end":2177.818112,"start":2171.784067}]
onPositionUpdated:  2177.727
onPositionUpdated:  2177.828
onPositionUpdated:  2181.008
onPositionUpdated:  2181.054
onPositionUpdated:  2182.056
onPositionUpdated:  2183.055
onPositionUpdated:  2185.711
onPositionUpdated:  2185.916
onPositionUpdated:  2186.721

6. Environment

  • SDK Version: 0.20.3719

  • App State: Foreground

  • OS Information

NAME="OS"
OE_VERSION="4.0.0"
OS_MAJOR_VERSION="1"
OS_MINOR_VERSION="1"
RELEASE_ID="2"
OS_VERSION="1.1"
BRANCH_CODE="VegaMainlineTvIntegration"
BUILD_DESC="OS 1.1 (VegaMainlineTvIntegration/4418)"
BUILD_FINGERPRINT="4.0.155683.0(3072cab629675a74)/4418N:user-external/release-keys"
BUILD_VARIANT="user-external"
BUILD_TAGS="release-keys"
BUILD_DATE="Wed Sep 03 05:40:19 UTC 2025"
BUILD_TIMESTAMP="1756878019"
VERSION_NUMBER="201010441850"

  • Player SDK: Headless / Shaka

  • Player SDK Version: [e.g. 1.23]

    • Video Codecs: h.264

    • Manifest Types: m3u8 HLS

7. Example Code Snippet / Screenshots / Screengrabs

Include any relevant code or component setup in React Native that can help reproduce the bug.

playerClient.registerBufferedRangesListener(          
{  (bufferedRanges: Array<ITimeRange>, _sessionId?: IPlayerSessionId) => {

console.log(JSON.stringify(bufferedRanges));

 },     sessionId  

});

Q: Would you like to be contacted to share your latest VPKG compiled with latest SDK:

If needed

Q: VPN or Login needed to verify functionality in VPKG?

No

Hi @Jon_Page ,

This has been reported to our internal team for investigation.

Thanks,
Rohit

Hi @Jon_Page ,

Thank you for your patience.
As per your Amazon representative, we are closing this post for now.

Please feel free to create a new post if you have issues.

Thanks,
Rohit