Site Isolation raises vpaid_adapter.js related ads not working.

[Elson Yeh]

Hi MA SDK Team,

I faced a VPAID ad issue on ad loading vpaid_adapter.js.

I know we should avoid such a creative, but unfortunately we can not control over the delivery side of the ad.

This kind of ad works fine in the Video Suite Inspector test, but after taking off the iframe of the Video Suite Inspector, we get the very high probability of 402 error.

We did a lot of testing and found the error related to Site Isolation enabled default on Chrome 67 and later. Once turning off this setting, the issue disappeared.

Can you clarify the following questions?

1. Is there a cross-process error when loading multiple ima3.js?

2. There are several ways to get around this problem:  

   - Require the delivery side not to serve the vpaid_adapter.js ad.

   - Wrap the website with an iframe, Like VSI.

   - Set the Vpaid mode to INSECURE mode.

   - Turn off Site isolation.

   Because of our production environment limitations, these solutions are not suitable for us.   Can you provide an API to exclude vpaid_adapter.js creative?

[ima-sdk-adv...@google.com]

Hi Elson,

Thank you for reaching out to us. We haven't been able to reproduce the issue on our end using our vpaid ad tag. Can you share your ad tag so we can investigate further?

Regards,

Deepika Uragayala

IMA SDK Team

--
You received this message because you are subscribed to the Google Groups "Interactive Media Ads SDK" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ima-sdk+unsubscribe@googlegroups.com.
To post to this group, send email to ima...@googlegroups.com.
Visit this group at https://groups.google.com/group/ima-sdk.
For more options, visit https://groups.google.com/d/optout.

[Elson Yeh]

Hi MA SDK Team,

I sent you a private message with the test vast xml. please refer to it. thank you.

Elson Yeh於 2018年10月9日星期二 UTC+8下午4時13分11秒寫道：

[ima-sdk-adv...@google.com]

Hi Elson,

Thank you for providing additional insights with regards to the issue. The VAST XML you shared above seems to be broken and throws errors you can see in the file attached when we're trying to host it. Can you share an ad tag url or fix the VAST XML before sharing it with us. It is most likely the iframe that your VPAID ad is not compatible with. If you can, I would suggest reaching out to the VPAID creative provider for more information about the ad. If you are the VPAID creative provider (as in, you developed this ad), you may want to take a look at our sample VPAID ad on GitHub.

Regards,

Deepika Uragayala

IMA SDK Team

On 10/09/18 04:13:11 div...@gmail.com wrote:

--

[Elson Yeh]

Hi IMA SDK Team,

I sent you a private message with the test vast xml again. Thanks for your help.

ima-sdk-adv...@google.com於 2018年10月11日星期四 UTC+8上午3時31分16秒寫道：

[ima-sdk-adv...@google.com]

Hi Elson,

Thank you for providing a proper VAST XML for our test purposes. We tested several times the VAST you provided using CHROME 69 with the Site Isolation feature enabled but were unable to encounter the AdError 402, that being said, there's no cross-process error when loading multiple ima3.js. Please note that the Site Isolation is an experimental feature of Chrome, enabling it can result in errors or unwanted behaviors of the browser.

Regards,

Deepika Uragayala

IMA SDK Team

[Elson Yeh]

Hi IMA SDK Team,

Please confirm the following two items to ensure that we test on the same basis:

1. Test on a VSI page that is not wrapped in an iframe.

Https://google-developers.appspot.com/interactive-media-ads/docs/sdks/html5/vastinspector_5ba2007beb4682c53068740df57bb596.frame

2. Confirm that the "Site Isolation" feature is enabled.

The link has a detailed description of how to confirm the enable and force enable or disable.

http://www.chromium.org/Home/chromium-security/site-isolation

The "Site Isolation" feature is still experimental, so not all Chrome is enabled.

But the normal user doesn't know it has been enabled or disabled.

From the report of our advertising, the proportion of encountering this problem is extremely high.

Regards,

Elson

ima-sdk-adv...@google.com於 2018年10月12日星期五 UTC+8上午3時03分09秒寫道：

[ima-sdk-adv...@google.com]

Hi Elson,

Thank you for getting back to us. We used your version of VSI (Not wrapped in an iframe) and enabled the Site Isolation feature (chrome://flags/#enable-site-per-process) on a Chrome version 69. We were not able to encounter the issue you reported.

Regards,

Deepika Uragayala

IMA SDK Team

[Elson Yeh]

Hi IMA SDK Team,

I don't know the reasons caused the difference between your environment and mine.

Is it possible because the time zone is different?

I am in Taipei, Taiwan, Asia.

I recorded the HAR file in the attachment, and the Performance JSON in this link

https://drive.google.com/file/d/1zQrBMq-6MSgWhO8Dwq-1dNogRRAi5Vvh/view?usp=sharing

Hope these could help you to clarify the problem.

Regards,

Elson

ima-sdk-adv...@google.com於 2018年10月13日星期六 UTC+8上午3時52分18秒寫道：

[ima-sdk-adv...@google.com]

Hi Elson,

Thank you for reaching out to us. The error code 402 usually occurs because the server fails serving the whole ad video to the SDK in 8 seconds delay. You can increase the delay by setting the loadVideoTimeout property as specified in the reference. However, our team does not recommend to modify the adapter tags within the IMA SDK. The adapter spins up it's own implementation of IMA, which is redundant and has been known to cause errors when modified.

Regards,
Deepika Uragayala
IMA SDK Team

[Elson Yeh]

Hi IMA SDK Team,

We have tried to adjust loadVideoTimeout to more than five minutes and there will still be a timeout error.

Actually, the movie has timed out before it has started loading, and this situation can be found from the last provided HAR file.

I noticed that when the bridge3.242.3_en.html cause by vpaid_adapter.js posted a "getPageSignals" message, the 402 error will be occurred definitely.

If the message "getPageSignals" is not posted, the ad can be played normally.

I don't know their relationship, but maybe you could find the mystery in it.

ima-sdk-adv...@google.com於 2018年10月16日星期二 UTC+8上午3時25分19秒寫道：

[ima-sdk-adv...@google.com]

Hi Elson,

Thank you for reaching out to us. We're not able to comment on their exact relationship as this is related to the internal workings of the SDK. Further, even if you were able to figure out their relationship and how to use them for your own reporting, I would not suggest doing so. It is always possible that the SDK's internal mechanisms will change. As mentioned before, we suggest that you use the direct tags instead of modifying the adapter tags to avoid these kind of errors.

Regards,

Deepika Uragayala

IMA SDK Team