-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
videojs.log.history is empty on iphone ios #8935
Comments
👋 Thanks for opening your first issue here! 👋 If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can. |
my code on react
|
videojs on iphone uses native hls player, and i think this is the reason why i cant access to player.on("error"... and reason why history array is empty, but event player.on("waiting"... works pretty good |
in my project we use history() to access to warnings and etc for using that to switch sources to lower resolution when cdn gives broken fragment |
iPhone's native playback won't necessarily trigger errors in the same conditions, nor does it log anything. It's a black box. Latest iOS on iPhone has support for Managed Media Source Extensions, with which we can play HLS with our VHS playback engine. It's still considered experimental - we don't know if we've seen every edge case yet - but you could try it out for your use case as detailed in the comment linked below. |
videojs.log.history is empty on iphone ios, i have a same bug on other versions of package, 6.x.x, 7.x.x, 8.x.x., work with a hls player, and i need to access to the log history, but only on iphone i have a empty array when use console.log(videojs.log.history())
waiting for your response about this problem, also in iphone i got bug with player.on("error"....., videojs cant handle errors, i dont know why, thats only problem in iphone, i have tested this in browserstack on iphone 15 safari and chrome browsers, and have tested it on my own iphone, also i have tested this on mac and windows on browserstack and all is good, no issues, and i tested it on my work mac and windows computer, and take the same result, problems only on iphone
The text was updated successfully, but these errors were encountered: