-
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
What to do when there's a problem with ad source? #3801
Labels
Comments
grajzer
changed the title
What to do when there's problem with ad source?
What to do when there's a problem with ad source?
Feb 5, 2018
Another example:
We expect a 403 and no ad to play but the video content does not play and the player hangs. For testing you can use the following VAST tag.
|
ojw28
pushed a commit
that referenced
this issue
Feb 16, 2018
This error marks the current ad group as unplayable. Issue: #3801 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=185663472
ojw28
pushed a commit
that referenced
this issue
Feb 20, 2018
This error marks the current ad group as unplayable. Issue: #3801 ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=185663472
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If there's a problem with ad, player just won't do anything. How to deal with this situation?
Here's an example ad tag URL you can use in exoplayer demo-ima app:
"https://vid.springserve.com/vast/183355?w=400&h=300&url=com.google&cb=1233445"
onAdLoadError is called and the following error is fired "AdErrorCode [name: VAST_LINEAR_ASSET_MISMATCH, number: 403], message: Linear assets were found in the VAST ad response, but none of them matched the video player's capabilities."
Exoplayer should continue playing the video in cases like this.
The text was updated successfully, but these errors were encountered: