-
Notifications
You must be signed in to change notification settings - Fork 468
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
Suppress player error during ad playback #2067
Comments
Sorry, 1st and 3rd media URI produce a HTTP 403 error, it is not intended. I guess they are no longer available now. I extracted these URLs from this adsTag |
Thanks for reporting. The player already skips ads that fail to load initially or have issues preparing. There is currently no mechanism to catch and ignore errors occurring later in the pipeline though (this includes DRM load errors). Is the failed DRM resolution a real example or was this just a way to test out if the player skips an ad? |
As apps embedding Media3 to play content with ads have often absolutely no control on what kind of ad media are delivered, the player might stop because of an unsupported media. It may be because of a low-end device not supporting non-traditional formats, or it may be because an ads provider could give a corrupted media file. So I think this use case should be handled by Media3, or at least there should be a warning on the documentation about this. What's your opinion? As a workaround, I setup a listener for
It seems to work fine, as next ads are played, and the content too.
No, it was just a way to test this behavior. Maybe |
Yes, I agree. We already handle the equivalent case for errors during initial media preparation (where most network related issues occur), so it's only logical to extend that to all errors happening during ad playback. And ideally this happens without ever surfacing the errors as a regular player error via |
Great! Thanks a lot! |
Version
Media3 1.5.1
More version details
No response
Devices that reproduce the issue
Any device
Devices that do not reproduce the issue
No response
Reproducible in the demo app?
Yes
Reproduction steps
When playing a content with ads (handled by IMA SDK and media3-exoplayer-ima), and a playback error occurs during an ad playback, then the player stops instead of playing next ads and/or content.
Code example:
In this example, the 2nd ad fails to play because it is DRM protected and the given license URL is wrong.
Expected result
Ads following the failed ad play, then the content plays.
Actual result
The player stops with an error.
Media
Not applicable
Bug Report
adb bugreport
to [email protected] after filing this issue.The text was updated successfully, but these errors were encountered: