-
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
IMA SDK AD_BUFFERING event prevents from firing any other event. #8270
Comments
Possibly related to #8239? |
@icbaker looks like it! |
@icbaker @andrewlewis this is affecting our prod app so we wouldl have to downgrade to exoplayer 2.11.X but we can't because 2.12 brings a fix to the companion banner on audio ads.. Do you think it will get prioritized to next version? Thanks |
I'm looking into this now. To be confirmed, but I think it's likely we'll be able to get a fix into a minor release soon (although this will need to be done carefully as |
I have a fix ready and it should be easy to cherry-pick into the next minor release. I'll mark this issue as a duplicate of the other one for now. Thanks! |
Duplicate of #8239 |
@andrewlewis Perfect! Thanks. |
[REQUIRED] Issue description
When Preloading an AD and playing it after, if the AD_BUFFERING Event is triggered, IMA SDK does not fire any other PROGRESS EVENT
[REQUIRED] Reproduction steps
Test with slow internet speed and receive a buffer before loading all ad.
Tested with DEMO TAG
Toggling enable preloading does not seem to affect anything..
[REQUIRED] Link to test content
Demo Tag https://pubads.g.doubleclick.net/gampad/ads?sz=640x480&iu=/124319096/external/single_ad_samples&ciu_szs=300x250&impl=s&gdfp_req=1&env=instream&output=vast&unviewed_position_start=1&cust_params=deployment%3Ddevsite%26sample_ct%3Dlinear&correlator=
and SilenceMediaSource after
[REQUIRED] A full bug report captured from the device
Full Log when Buffer fire:
Full Log Without:
[REQUIRED] Version of ExoPlayer being used
2.12.1
[REQUIRED] Device(s) and version(s) of Android being used
Tested with Android 6,8,9,10,11
The text was updated successfully, but these errors were encountered: