Skip to content

[BUG]: (iOS) onReadyForDisplay not firing for some HLS videos #4561

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ivaniuk7531 opened this issue Jun 2, 2025 · 4 comments
Open

[BUG]: (iOS) onReadyForDisplay not firing for some HLS videos #4561

ivaniuk7531 opened this issue Jun 2, 2025 · 4 comments

Comments

@ivaniuk7531
Copy link

ivaniuk7531 commented Jun 2, 2025

Version

6.14.1

What platforms are you having the problem on?

iOS

System Version

iOS - 18.4.1

On what device are you experiencing the issue?

Real device, Simulator

Architecture

Old architecture

What happened?

I'm using the Video component to play HLS streams in my app. For some specific HLS URLs, the onReadyForDisplay callback is never triggered. As a result, I can hear the audio, but the screen only shows the loader, and the video never appears.

Screen.Recording.2025-06-02.at.13.03.13.mov

Reproduction Link

https://github.com/ivaniuk7531/react-native-video-HLS-error/tree/hls-onReadyForDisplay

Reproduction

Steps to reproduce this bug are:

  1. Clone the repository and install all dependencies;
  2. Run the app on a physical device or Android emulator;
  3. Wait for the video to load.
Copy link

github-actions bot commented Jun 2, 2025

Previous bot comment (click to expand)

Hey! 👋
Thanks for reporting this issue. We try to fix bugs as quickly as possible, but since our time is limited, we prioritize sponsored issues first, then focus on critical problems affecting many users, and finally, we handle other reports when we can. Some issues might take a while to be resolved.

If you want to speed up this process, check out Issue Boost – it allows us to dedicate time specifically to your issue and fix it faster.

Thanks for your patience and support! 🚀

Copy link

github-actions bot commented Jun 2, 2025

Previous bot comment (click to expand)

Hey! 👋
Thanks for reporting this issue. We try to fix bugs as quickly as possible, but since our time is limited, we prioritize sponsored issues first, then focus on critical problems affecting many users, and finally, we handle other reports when we can. Some issues might take a while to be resolved.

If you want to speed up this process, check out Issue Boost – it allows us to dedicate time specifically to your issue and fix it faster.

Thanks for your patience and support! 🚀

1 similar comment
Copy link

github-actions bot commented Jun 2, 2025

Previous bot comment (click to expand)

Hey! 👋
Thanks for reporting this issue. We try to fix bugs as quickly as possible, but since our time is limited, we prioritize sponsored issues first, then focus on critical problems affecting many users, and finally, we handle other reports when we can. Some issues might take a while to be resolved.

If you want to speed up this process, check out Issue Boost – it allows us to dedicate time specifically to your issue and fix it faster.

Thanks for your patience and support! 🚀

Copy link

github-actions bot commented Jun 2, 2025

Hey! 👋
Thanks for reporting this issue. We try to fix bugs as quickly as possible, but since our time is limited, we prioritize sponsored issues first, then focus on critical problems affecting many users, and finally, we handle other reports when we can. Some issues might take a while to be resolved.

If you want to speed up this process, check out Issue Boost – it allows us to dedicate time specifically to your issue and fix it faster.

Thanks for your patience and support! 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: To Triage
Development

No branches or pull requests

1 participant