-
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
AdEvent.ALL_ADS_COMPLETED called prematurely #7041
Comments
Please do send the ad tag URL to dev.exoplayer@gmail.com. Thanks. |
Hello Andrew, I sent the ad tag URL to the email. Subject: Issue #7041 |
The ad tag is unfortunately now empty. Please could you try to reproduce this on the |
Hey Andrew, it looks the issue is resolved using dev-v2 What would be the timeline for this release? Thanks a bunch! |
Glad to hear that it's fixed. We generally don't give a concrete timeline as unexpected things can come up but I expect it will be within the next week or two. |
I've been noticing some strange behaviour associated with the IMA ExoPlayer extension, not too sure if it's intended or not. When loading a pre-roll ad where there are multiple ads served, if I background the app while the last ad is playing (ie. 2 of 2) I get returned an AdEvent.ALL_ADS_COMPELETED. As a result, when returning to the app, rather than continuing the ad, it finishes and proceeds to play the content.
If I do the same steps but on the first ad (ie. 1 of 2), it pauses then resumes as intended. Behaviour is also fine when one ad is served.
I can provide more information if needed. I can also send an ad URL via email if needed as well.
Reproducible on the demo app
Version(s) used: 2.9.1 & 2.11.3
The text was updated successfully, but these errors were encountered: