You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The API doc says the response property should be an object, not a string:
Hls.ErrorDetails.FRAG_LOAD_ERROR - raised when fragment loading fails because of a network error
data: { type : NETWORK_ERROR, details : Hls.ErrorDetails.FRAG_LOAD_ERROR, fatal : true or false, frag : fragment object, response : { code: error code, text: error text } }
The description and error message suggests that a custom loader implemented outside of this project is being used. The loader is responsible for its output and for adhering to the interface, types, and expectations set forth in the documentation.
What version of Hls.js are you using?
1.2.1
What browser (including version) are you using?
Brave 1.42.88 Chromium: 104.0.5112.81
What OS (including version) are you using?
macOS Version 12.5
Test stream
No response
Configuration
Additional player setup steps
No response
Checklist
Steps to reproduce
hls.on(Hlsjs.Events.ERROR, (event, data) => console.log(data))
Expected behaviour
What actually happened?
The response property is a string containing what should be in
response.text
.Console output
The text was updated successfully, but these errors were encountered: