[IMA-SDK HTML5] Tizen TV VMAP Issue – allAdsCompleted Triggering After First Ad

[Sumit Kumar Dey]

Hi team,

Device Information:

Tizen TV

SDK Details:

<script src="https://cdnjs.cloudflare.com/ajax/libs/shaka-player/4.10.9/shaka-player.ui.min.js" defer></script>

<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/shaka-player/4.10.9/controls.min.css">

<script src="https://imasdk.googleapis.com/js/sdkloader/ima3_debug.js"></script>

Problem:
We are using VMAP with three ads scheduled at 5s, 10s, and 15s.

On Tizen TV, the player successfully plays the first ad, but after it finishes, the player fires the ad-stopped event twice:

• 1st ad-stopped event: e.originalEvent.type is giving allAdsCompleted
• 2nd ad-stopped event: e.originalEvent.type is giving contentResumeRequest

Because of this, the second and third ads are skipped.

Question: 

Why is allAdsCompleted firing immediately after the first ad finishes?

Example of VMAP:

<?xml version="1.0" encoding="UTF-8"?>

<vmap:VMAP xmlns:vmap="http://www.iab.net/videosuite/vmap" version="1.0">

<vmap:AdBreak timeOffset="00:00:5" breakType="pre-roll" breakId="preroll-1">

<vmap:AdSource id="midroll-1-ad-1" allowMultipleAds="false" followRedirects="true">

<vmap:AdTagURI templateType="vast3"><![CDATA[ https://pubads.g.doubleclick.net/gampad/ads?iu=/21775744923/external/single_ad_samples&sz=640x480&cust_params=sample_ct%3Dlinear&ciu_szs=300x250%2C728x90&gdfp_req=1&output=vast&unviewed_position_start=1&env=vp&correlator=]]></vmap:AdTagURI>

</vmap:AdSource>

</vmap:AdBreak>

<vmap:AdBreak timeOffset="00:00:10" breakType="mid-roll" breakId="midroll-2">

<vmap:AdSource id="midroll-1-ad-2" allowMultipleAds="false" followRedirects="true">

<vmap:AdTagURI templateType="vast3"><![CDATA[https://pubads.g.doubleclick.net/gampad/ads?iu=/21775744923/external/single_ad_samples&sz=640x480&cust_params=sample_ct%3Dlinear&ciu_szs=300x250%2C728x90&gdfp_req=1&output=vast&unviewed_position_start=1&env=vp&correlator=]]></vmap:AdTagURI>

</vmap:AdSource>

</vmap:AdBreak>

<vmap:AdBreak timeOffset="00:00:15" breakType="post-roll" breakId="postroll-3">

<vmap:AdSource id="midroll-1-ad-3" allowMultipleAds="false" followRedirects="true">

<vmap:AdTagURI templateType="vast3"><![CDATA[https://pubads.g.doubleclick.net/gampad/ads?iu=/21775744923/external/single_ad_samples&sz=640x480&cust_params=sample_ct%3Dlinear&ciu_szs=300x250%2C728x90&gdfp_req=1&output=vast&unviewed_position_start=1&env=vp&correlator=]]></vmap:AdTagURI>

</vmap:AdSource>

</vmap:AdBreak>

</vmap:VMAP>

Regards,
Sumit

[IMA SDK]

Hi Sumit,

Thank you for contacting IMA SDK support team.

I will check with our team and get back to you with an update as soon as possible. In the meantime, your patience is appreciated.

Thanks,
 

IMA SDK Team

Feedback
How was our support today?

               
[2025-11-19 22:56:15Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vTyw7:ref" (ADR-00344061)

[IMA SDK]

Hi,

Thank you for reaching out to the IMA SDK Support team.

I reviewed the provided VMAP XML and was able to reproduce the same behavior. This is expected, as you are using the same VAST tag for all ad breaks (pre-roll, mid-roll, and post-roll). As a result, only the pre-roll ad plays, while the remaining ad breaks receive empty responses. According to the documentation, if you need to request ads with the same VAST tag more than once, you must indicate to the ad server that these are valid, intentional requests rather than duplicates.The SDK does this for you with two quick API calls:

1. Call destroy() on your AdsManager instance. This prevents any post-rolls from playing when you make the below call to contentComplete(). You get a new AdsManager when you make your next request.

2. Call contentComplete() on your AdsLoader instance. This resets the SDK so the new ad request doesn't look like a duplicate of the previous one.

After making the two calls above, you can call requestAds() on your AdsLoader instance to get another set of ads to play for your new video. Otherwise try with different VAST tags for all ad breaks.

Thanks,

 

IMA SDK Team

Feedback
How was our support today?

               

[2025-11-24 07:26:34Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vTyw7:ref" (ADR-00344061)