androidx / androidx/media

The events triggered by the ad content are misfired when manually requesting ad using the Interactive IMA SDK.

Open
#2,374 4 comments 0 reactions 1 assignee View on GitHub

@marcbaechinger is already working on this.

Since Apr 25, 2025.

wont fix: app issue
Dominant language
Java
Stars
3k
Forks
955
Avg merge
12d 14h
Merged PRs (30d)
2

Description

Version

Media3 1.6.1

More version details

No response

Devices that reproduce the issue

problem is with al the devices

Devices that do not reproduce the issue

No response

Reproducible in the demo app?

Yes

Reproduction steps

When I am trying to send the ad request manually using the Interactive IMA SDK library which creates a VideoAdPlayer interface object, it is able to send the request and the ad is playing in the ExoPlayer, but:

The events triggered by the ad content are misfired.

Major Ad events like:

skipped

first quartile

midpoint

etc.

are never triggered/fired.

This results in:

Triggering all_ads_completed and content_resume_requested early (like after 4 or 5 seconds of ad play) even though the ad content is of 20–28 seconds.

Also, the skip button is not displaying in the skippable ads.

Expected result

all the events must be triggered that are sent back by VideAdPlayer interface , get adprogress is never triggered of vdieoAdPlayer

Actual result

Major Ad events like:

skipped

first quartile

midpoint

etc.

are never triggered/fired.

This results in:

Triggering all_ads_completed and content_resume_requested early (like after 4 or 5 seconds of ad play) even though the ad content is of 20–28 seconds.

Also, the skip button is not displaying in the skippable ads.

Media

yes can be reproduced by manually firing ad request using Interactive IMA SDK library

Bug Report
  • You will email the zip file produced by adb bugreport to android-media-github@google.com after filing this issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.