-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Decryption failure with wrong key does not trigger ERROR listener #5250
Comments
Here is my configuration:
Here is the console output, it appears to be trying to decrypt each frag, so the output is duplicated
|
Hi @lim-kim930, I see from the logs it's failing with You can expect this to produce a FRAG_PARSING_ERROR. |
You can preview the changes here https://deploy-preview-5241--hls-js-dev.netlify.app/demo/ |
Duplicates #5011 |
Thanks a lot, I did see the error output in the preview version, looking forward to the 1.4.0 version. |
Marking as fixed in v1.4.0. |
What do you want to do with Hls.js?
When I specified the wrong KEY in the m3u8 file, I found that hls.js will request all the remaining fragments after requesting the key file. I want to stop loading after judging that the decryption fails, so I set the ERROR listener. However, I I found that it was not triggered, is there any usage I missed?
What have you tried so far?
No response
The text was updated successfully, but these errors were encountered: