-
Notifications
You must be signed in to change notification settings - Fork 10
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
[BUG]onPlayerError/onSetupPlayer error are not being called on native side or they do not expose any error codes via bridge #63
Comments
This should be resolved in the main branch now as of merging #96. This will be packed into the next release to NPM. |
@Jmilham21 First I would like to thank you for looking into this issue. I've tested the new code.
Info:
|
Description
Android: onPlayerError/onSetupPlayer are not called when there is an error regarding the
hlsUrl
or the signature token.iOS: - when there is a video play error (invalid hls url or expired token)
onPlayerError
is not called. Instead, theonSetupPlayerError
is called andevent?.nativeEvent
does not contain enough data for error handling in react native:Object should contain the error code. In case token is expired a fetch from BE could be done to obtain a new valid
hlsUrl
To Reproduce
Expected behavior
In case of any player or setup error at least one of the error functions should be called and the error code should be exposed in the nativeEvent object.
Screenshots / Visual evidence
Player displays error codes but these are not included in the nativeEvent or the onError functions are not being called.

The text was updated successfully, but these errors were encountered: