-
Notifications
You must be signed in to change notification settings - Fork 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
Document most common ExoPlaybackException causes #1611
Comments
Does the cause returned by |
Hi Andrew, with the cause I can get some information in some cases surfing the code. But probably it's more user friendly to have a list with the different kinds of errors I can get from the player. |
As per #1552, it's not possible to provide a complete list of errors, but I agree it would be useful to have documentation listing the most common/important exceptions. I'll use this issue to track adding the documentation. Thanks! |
Hi, |
It's been a while, but one way to address this finally would be to implement a more comprehensive |
#minor-release Issue: #1611 PiperOrigin-RevId: 385741535
This will be addressed by |
My request is to set a more intelligent error management instead of always launching a ExoPlaybackException. This makes very difficult to shown information to the user about the player error.
The ideal solution was to return different error codes for different errors to know the cause of the error
The text was updated successfully, but these errors were encountered: