8000 The events triggered by the ad content are misfired when manually requesting ad using the Interactive IMA SDK. · Issue #2374 · androidx/media · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

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

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.

Sign up for GitHub

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

Jump to bottom
Open
1 task
Aditya30081 opened this issue Apr 25, 2025 · 4 comments
Open
1 task

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

Aditya30081 opened this issue Apr 25, 2025 · 4 comments
Assignees
@marcbaechinger
Labels
wont fix: app issue

Comments

@Aditya30081
Copy link

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
@Aditya30081 Aditya30081 changed the title The events triggered by the ad content are misfired using the Interactive IMA SDK. The events triggered by the ad content are misfired when manually requesting ad using the Interactive IMA SDK. Apr 25, 2025
@marcbaechinger marcbaechinger self-assigned this Apr 25, 2025
@marcbaechinger
Copy link
Contributor

If you are using the IMA library directly, then I don't think we can help with that I'm afraid. You need to talk to the IMA ads team for direct SDK support.

If I have misunderstood, and you are using the ImaAdsLoader or another Media3 API that talks to the SDK, then please clarify what your setup with Media3 APIs is. To make this actionable for use we would need to be able to repro this is the demo app to be able to help you efficiently.

@Aditya30081
Copy link
Author

Hey , i reached out here because when i tried to trigger manual request using interactive IMA sdk with videoview events are triggered properly as expected but when triggering manual ad request with media3 then the ad events are not triggered properly.
Can you just try and help me with triggering manual adRequest using interactive IMA SDK and playing the ad content with all the events triggered

@marcbaechinger
Copy link
Contributor
marcbaechinger commented Apr 25, 2025 •
edited
Loading

Thanks for your response.

As I said I think we aren't the right folks to look into this. There is no Media3 API that uses manual ad request.
I think #1972 asks for implementing this with the ImaAdsLoader, but currently Media3 isn't using this feature.

However, if you are using the IMA SDK API directly, we can't help with this I'm afraid.

If you think the problems you are seeing is cause by Media3, please narrow down your question to a concrete suggestion why Media3 is causing this problem and provide some repro steps that make this issue actionable for us.

@Aditya30081
Copy link
Author

Hey thanks for your response,
You are correct there isn't any media3 API that uses manual ad request and that's why I am trying to simply trigger a manual ad request using the Interactive IMA SDK instance that created a VideoAdPlayer interface instance which binds the ad response received to the simple media3 playerView instance and starts rendering it. The issue specifically is that when the ad is rendered in media3 playerView there are few events of the ad lifecycle that are triggered using the getAdProgress overridden method inside the IMA SDK's VideoAdPlayer interface which interacts with the media3 playerView in which the ad is displaying and triggers those events and somehow those events are incorrectly triggered maybe due to improper setup of media3 instance and manual ad request of IMA SDK .
Now, what I actually want your help with is please if could reproduce this and try and steps for reproducing:

  • create a media3 playerView instance
  • create a manual ad request using the interactive IMA SDK which would couple with the media3 video view itself .
  • and then check for all the ad content lifecycle events which would miss all the major events required to integrate video ads efficiently in the Videoplayer.(missed events : skipped, first quartile , ad started , midpoint , second quartile etc.)

Also I would need your suggestion in one thing that media3 itself is handling this manual ad request system in its media3.ima extension which must be firing the ad request manually only using the interactive IMA SDK in its internal class and when used that for first preroll ad request using media3.ima extention ad events are triggered properly as expected . So if I want to use the same way the things are done inside the media3.ima extension would that be possible for me to achieve and if yes , is there any way you can help me with that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@marcbaechinger marcbaechinger

Labels
wont fix: app issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@marcbaechinger @Aditya30081
0