Subsequent Ad Calls Result in a 402: VAST media file loading reached a timeout... AFTER the ad is already playing followed by a 900: nvalid usage of the API. Cause: An ad has not been selected.

[Frank Turano]

First ad request goes out. Ad plays. Reset adsManager. Next ad request goes out. Second ad starts to play and then mid playback we get a 402, usually followed by a 900. Seems like maybe the adTimeout does not reset to 0?

[IMA SDK]

Hi Frank,

Thank you for reaching out to us. It seems to be an issue with the ad tag you are using, some of your MediaFiles bitrate might be too heavy for the video's first frame to be loaded before the 8 seconds delay. Can you share the ad tag you were using when you encountered this issue? You can share it privately by using the Reply privately to author option.

Regards,
Arnaud Casame
IMA SDK Team

ref:_00D1U1174p._5001UHHhP1:ref

[Frank Turano]

So the timeout error occurs after the second ad is already playing. I can reproduce this even using the provided sample vpaid ad.

[IMA SDK]

Hi Frank,

The 402 error code is a fatal error can be caused by a problem fetching or playing the MediaFile, and could be any of the following:

• The loadVideoTimeout is set too low in the IMA SDK. The default is 8 seconds.
• Low bandwidth or poor website implementation with competing requests that delay loading of the MediaFile.
• A video auto-plays in a mobile environment, whereas it should be click-to-play (there are some exceptions).
• Showing video ads in an auto-play environment (for example, a playlist), while the window is not in focus (either another tab is selected, or window is minimized).*

For players that use the IMA SDK, video fallback may be helpful to avoid losing impressions.

To solve this issue, the recommended actions are:

• Increase the timeout limit of your player via the SDK. Learn more (assuming that you're using the IMA SDK for HTML5)
• Ensure that any CDN-hosted creatives are returned within the specified media timeout.