Media 3 player does not resume once the Ad creative load is blocked via Charles/Adblockers
@marcbaechinger is already working on this.
Since Sep 12, 2024.
- Dominant language
- Java
- Stars
- 3k
- Forks
- 955
- Avg merge
- 12d 14h
- Merged PRs (30d)
- 2
Description
Version
Media3 main branch
More version details
No response
Devices that reproduce the issue
Pixel 7A Android 14
Devices that do not reproduce the issue
No response
Reproducible in the demo app?
Yes
Reproduction steps
- Add Charles proxy support in the project or install an ad blocker or any another tool that blocks ads urls such as
imasdk.googleapis.com - Add the ad creative domains in Charles's blocklist
imasdk.googleapis.com - Start media playback with preproll ad
Expected result
The player shouldn't be blocked and the playback should be started or we should get some error callback notifying why the player is stuck
Actual result
The player is blocked , the playback has not started and we don't receive any callback on this state.
For information, the issue can be reproduced on media 3 sample app easily. On our application, we estimate that a few thousands of our users are facing the issue and they remain blocked when they try to start a playback.
This issue has already been reported in issue link
Media
Not applicable
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.