All ads in VMAP rejected as invalid if one ad is bad

[BC]

If a VMAP response contains an invalid ad, all ads a rejected as invalid with the message "Non-fatal error occurred: The response does not contain any valid ads." Error event beacons are sent for the bad ad. No events are sent for the other ads.

The behaviour I expecting is that the valid ads would play.

Example: https://test.misterben.me/vmap_with_bad_wrapper.xml

In this example, simplified from a response received in the wild, the bad ad is a wrapper. The response at VASTAdTagURI is another wrapper, where the VASTAdTagURI is not a valid URL. 

      <VASTAdTagURI>

        <![CDATA[https://]]>

      </VASTAdTagURI>

The same behaviour is observed if this URL is replaced with one that returns 404.

(Apologies for the mangled post just now, fat fingers)

[IMA SDK]

Hi,

Thank you for reaching out to us. We've tested your ad tag against our VSI and encountered the same issue (see error_msg screenshot attached). However, when I tried to open your VAST XML in a browser tab, it fails the XML parsing process (see xml_parse screenshot attached). We would recommend you to reach out to your ad provider so they can help you fix your VAST XML.

Regards,
Arnaud Casame
IMA SDK Team

ref:_00D1U1174p._5001UHI2vz:ref

[BC]

Sorry, the missing closing tag was introduces in creating the repro case. I've fixed that, and that was not the cause of the issue reported.

[IMA SDK]

Hi,

Thanks for fixing the VAST XML. We've extracted and tested the VAST XML against our VSI and received the error message saying that none of the ads are valid (see vast_error screenshot attached). We've also extracted the ads individually and ran them against the VSI, the first ad threw the AdError 400, which means that the SDK player was not able to play the video ad. When we tested the MediaFile url found in the VAST XML against the browser, the server return an error code 403 (see forbidden screenshot attached). The second ad which is wrapper threw an error code 301 meaning that the ad request reached a timeout (see request_timeout screenshot attached). It is important to note that none of these errors are caused by the IMA SDK, they are issues coming from the embedded ads. We would recommend you to follow the recommendations specified by the Resolve VAST and IMA SDK errors so that you can solve the issues.