TypeError: Illegal constructor when calling AdDisplayContainer

[Joe Simon]

Hi team,

We recently started noticing a "TypeError: Illegal constructor" error after calling the AdDisplayContainer constructor. Any idea what could be causing this? It doesn't happen on every ad.

I attached stack trace as well.

Thanks!

[IMA SDK]

Hi Joe,

Thanks for your message.

Would just like to confirm which of the IMA SDK for HTML5 are you using here, is it the Client-side or the DAI? Could you also replicate this error using our video inspector (Client-side / DAI) If yes, kindly share with us the ad tag or CMS/Video ids that you are using so we could check on our end as well. You can share this information with us by sending to our email alias: imate...@gmail.com

Regards,

Sherwin Diesta IMA SDK Team

ref:_00D1U1174p._5004Q23v3vP:ref

[Chris.T...@dowjones.com]

Client side HTML5 SDK

Version was whatever was the latest as of 11PM EDT last night when we observed the error.  When we checked the release notes it was 3.404.1, but I noticed when I just checked this morning, I'm now seeing  3.404.2 which is listed as a service release from (late?) yesterday.

What was fixed in the service release?  This issue perhaps?

[David]

I haven't been able to replicate this in the video inspector, but could use some insight in to why this error might be occurring.  It's difficult to replicate, but I've been able to see it consistently after 20 or so refreshes and trying to play the video at the top on wsj.com homepage.  Chrome incognito.

The below line of code is run in the IMA library every time this issue occurs then this line is what causes the error: Illegal constructor.

return r.Reflect.construct(HTMLElement, [], this.__proto__.constructor)

This code only seems to run when this issue happens.  It might be helpful to know what the purpose of that code is and why it runs in this case.  When this error occurs both players on the page fail and do not run ads.

Thanks

[IMA SDK]

Hi David,

I work with Sherwin and will assist you. I tried replicating the error without success. We haven't seen such an error come up recently.

There's no bug fix in the latest release, if a release of our SDK fixes something we would make a note of the fix.

We cannot discuss inner workings of the SDK.

We recommend that you match up your implementation with our sample apps.

Regards,

Aryeh Baker IMA SDK Team

ref:_00D1U1174p._5004Q23v3vP:ref