Midroll playback issue with the first AD Unit (Exoplayer) - first ad unit is skipped
Open
@marcbaechinger is already working on this.
Since Mar 20, 2024.
bug
needs triage
- Dominant language
- Java
- Stars
- 3k
- Forks
- 955
- Avg merge
- 12d 14h
- Merged PRs (30d)
- 2
Description
Version
Media3 1.1.1 / ExoPlayer 2.19.1
More version details
No response
Devices that reproduce the issue
Mobile phones with Android O.S
Devices that do not reproduce the issue
None
Reproducible in the demo app?
Not tested
Reproduction steps
- Launch an Irish VPN (to have access to our Google campaigns which are targeted only to Ireland country);
- Install and launch the attached sample app (Basic sample app with Media3 integration (v.1.1.1) and IMA SDK integration) (sample app also available here: https://finconsspa-my.sharepoint.com/personal/mauro_defeo_finconsgroup_com/_layouts/15/onedrive.aspx?id=%2Fpersonal%2Fmauro%5Fdefeo%5Ffinconsgroup%5Fcom%2FDocuments%2FFreeStream%2BIrishAdv%2Ezip&parent=%2Fpersonal%2Fmauro%5Fdefeo%5Ffinconsgroup%5Fcom%2FDocuments&ga=1)
- Play the media content configured in the sample app (DRM free content)
- Seek to minute 27:30
- Wait for minute 28:00 where the mid-roll slot should begin
Expected result
At minute 28 mid-roll slot should begin and play successfully
Actual result
Mid-roll slot begins at minute 28:08 as the first ad unit has been skipped and ADV playback starts from the second ad unit.
Media
Media content: https://www.emmanuelevilla.com/2048895036-50037512-c42f26a3-505c-4131-951f-8700b36d881d.mp4
Bug Report
- You will email the zip file produced by
adb bugreportto android-media-github@google.com after filing this issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.