-
-
Notifications
You must be signed in to change notification settings - Fork 3k
[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
Comments
Previous bot comment (click to expand)Hey! 👋 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! 🚀 |
Previous bot comment (click to expand)Hey! 👋 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
Previous bot comment (click to expand)Hey! 👋 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! 🚀 |
Hey! 👋 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! 🚀 |
Uh oh!
There was an error while loading. Please reload this page.
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:
The text was updated successfully, but these errors were encountered: