VPAID Tags not loading

tulika bose

unread,

Aug 22, 2016, 11:24:21 AM8/22/16

to Interactive Media Ads SDK

Hi Team,

We are facing issue in loading VPAID creatives.. Our player is an HTML5 player and usually it throws 901 errros.. Could you please check and help us with a workaround to load such ads?

Below are some details -

Test page - http://dummy.bhaskar.com/dummytech/demo-partner-1.html

VAST TAG - http://pubads.g.doubleclick.net/gampad/ads?sz=400x300&iu=/28928716/db_video_test&impl=s&gdfp_req=1&env=vp&output=xml_vast3&unviewed_position_start=1&hl=en&url=http://ultima.bhaskar.com/videos/the-man-clinging-to-the-road-232946-22483.html&description_url=http://ultima.bhaskar.com/videos/the-man-clinging-to-the-road-232946-22483.html&correlator=1471879000956&scor=1471879000956

Appreciate your quick revert

Thanks,

Tulika

Vu Chau (IMA SDK Team)

unread,

Aug 22, 2016, 2:35:35 PM8/22/16

to Interactive Media Ads SDK

Hi Tulika,

The issue appears to be stemming from the VPAID's source code (AdError 901: An unexpected error occurred within the VPAID creative. Refer to the inner error for more info. Caused by: Error: Error: Cannot read property 'fullscreenEnabled' of undefined).

Would you be able to test with other VPAID tags, as well, to see if there is a difference? You can find a few JS VPAID samples in this GitHub repo.

Vu Chau

IMA SDK Team

Vu Chau (IMA SDK Team)

unread,

Aug 22, 2016, 3:32:24 PM8/22/16

to Interactive Media Ads SDK

Hi Tulika,

Having looked into this issue some more, we think we have identified the culprit. What happens is that when you request the tag using the ENABLED mode, we spawn a proxied video element and render the ad there. Some HTML5 playback events might not be proxied over, though. If you request the ad in the INSECURE mode, then you can see that there is no error, because we don't proxy your video element in this mode.

As a workaround, you can initialize your adDisplayContainer in INSECURE, and the error should be gone immediately. If you have control over the ad, catch the error and return true for fullscreenEnabled.

I have raised a feature request to support fullscreenEnabled in our proxied video element. I will give you an update when I hear back from the rest of the team.

Vu Chau

IMA SDK Team

tulika bose

unread,

Aug 25, 2016, 1:33:01 PM8/25/16

to Interactive Media Ads SDK

Thanks VU for your suggestion! We have tried that.. Though it has served 901 errors but now we are seeing 301 errors..

VAST Tag - http://pubads.g.doubleclick.net/gampad/ads?sz=400x300&iu=/28928716/db_video_Janiye_Abhi&impl=s&gdfp_req=1&env=vp&output=xml_vast3&unviewed_position_start=1&hl=en&url=http://www.bhaskar.com/&description_url=http://www.bhaskar.com/&correlator=1472146217282&scor=1472146217282

Site: http://www.bhaskar.com/

Can you please check and let us know what is causing this?

Best,

Tulika

Vu Chau (IMA SDK Team)

unread,

Aug 25, 2016, 1:52:04 PM8/25/16

to Interactive Media Ads SDK

Hi Tulika,

That tag works fine in the VSI. On your homepage I also saw an ad.

A '301' does mean there is a timeout trying to load the VAST XML. Make sure you test on a strong connection, or feel free to share with us another tag where the error consistently occurs.

Vu Chau

IMA SDK Team

tulika bose

unread,

Aug 26, 2016, 3:06:02 AM8/26/16

to Interactive Media Ads SDK

Hi VU,

Yes you're right that ads are rendering but approx. 50% of times its showing 301 or 303 errors.. We would like to understand the reason of these errors and how we could solve this?

Thanks,

Tulika

Binny Patel (IMA SDK Team)

unread,

Aug 26, 2016, 11:30:28 AM8/26/16

to Interactive Media Ads SDK

Hi Tulika,

Vu is OOO so I will be handling this case on his behalf.

We have already discussed the 301 and 303 errors previously. Both of these AdErrors, 301 and 303, are pointing to the multiple of wrappers in your VAST XML.

The AdError 301 occurs due to multiple <VASTAdTagURI> creatives, which can fail to load due to any of these reasons (Invalid URI, unreachable or request timeout for URI, and security).
The AdError 303 occurs due to the no ads in the VAST response after one or more wrappers.

I would suggest you to reduce the wrappers and make sure that VAST creatives inside the wrappers are valid. Let me know if you have any other questions.

Thanks,

Binny Patel

IMA SDK Team

tulika bose

unread,

Aug 27, 2016, 12:56:50 AM8/27/16

to Interactive Media Ads SDK

Hey Binny,

I understand the logic behind these errors, but the reason why I have reached out to you if you have any workaround for this say reduction of timeout from partner server or some other technical suggestion if you can help us with..

Looking forward for your response..

Thanks,

Tulika

Binny Patel (IMA SDK Team)

unread,

Aug 29, 2016, 2:12:07 PM8/29/16

to Interactive Media Ads SDK

Hi Tulika,

I understand your concern, but there is no other workaround besides the suggestions I gave previously.

Thanks,

Binny Patel
IMA SDK Team

Vu Chau (IMA SDK Team)

unread,

Oct 13, 2016, 1:03:31 PM10/13/16

to Interactive Media Ads SDK

Hi Tulika,

Just an update that the following has been fixed:

The issue appears to be stemming from the VPAID's source code (AdError 901: An unexpected error occurred within the VPAID creative. Refer to the inner error for more info. Caused by: Error: Error: Cannot read property 'fullscreenEnabled' of undefined).

The change now allows fullscreenEnabled to be forwarded to the proxied video element when the VPAID ad is rendered in the ENABLED mode. This will allow the VPAID ads to go fullscreen. I'm unable to verify with your original ad tag since it is now returning empty VAST.

The fix should go live in a future release of the SDK. Please monitor our release notes for an update.