OmidVerificationVendor missing from google.ima in HTML5 SDK

[Arnaud Leyder]

Hi,

I am trying to follow Setting access mode rules for a request 

https://developers.google.com/interactive-media-ads/docs/sdks/html5/client-side/omsdk?hl=en#setting_access_mode_rules_for_a_request

I get an error each time TypeError: Cannot read properties of undefined (reading 'MOAT')

I am trying to read google.ima.OmidVerificationVendor.MOAT but while google.ima.OmidAccessMode seems to be defined the google.ima.OmidVerificationVendor property is undefined (and then I cannot read any specific vendor).

Am I missing something here?

Thanks

Arnaud

[IMA SDK]

Hello Arnaud,

 

I'm Michael from IMA SDK Team, thank you for reaching out to us.

 

Have you check our sample apps and tested if the same behavior is reproducible there? It is recommended to pattern your own integration with our working sample apps to avoid implementation issues.

 

If you have done the ask above and still encounter the issue, please share to us the sample project implementation you are working on to test on our end. Kindly share also the SDK version and the step by step process we need to do in order to replicate the same behavior. This will greatly help us for further investigation on the issue.

You may send the requested details privately via "Reply To Author" button.

Regards,

Michael Angelo Legaspi IMA SDK Team

ref:_00D1U1174p._5004Q2TOJCw:ref

[Arnaud Leyder]

Hi,

I am able to confirm that the issue is within the Google HTML5 IMA SDK not with our implementation.

Just go to https://googleads.github.io/googleads-ima-html5/vsi/ and open your browser console and type google.ima.OmidVerificationVendor.MOAT as shown in https://developers.google.com/interactive-media-ads/docs/sdks/html5/client-side/omsdk

This will spit an error:

TypeError: Cannot read properties of undefined (reading 'MOAT')

The OmidVerificationVendor property is not defined on google.ima namespace. If you type google.ima.OmidAccessMode.LIMITED then you will see it properly defined. This makes the docs under "Setting access mode rules for a request" unusable.

Thanks

Arnaud

[IMA SDK]

Hello Arnaud,

 

Thank you for responding back to us. However, we cannot reproduce the issue on our end. Would you be able to share with us the following information so we can further investigate on the issue?

• Screen recording of the behavior (step by step process to replicate the issue)
• Ad Tag used in request call
• Shareable sample project implementation (if possible)

[Dejan Grbavcic]

Hi guys,

Any update on this issue because it definitely exists? 

You can simply test it by implementing IMA on the page and then looking at google.ima object in the console. 
<script src="//imasdk.googleapis.com/js/sdkloader/ima3.js"></script>

There's no "OmidVerificationVendor" property!

If this isn't enough, you can also open ima3.js file and you'll see "OmidVerificationVendor" doesn't exist anywhere, while "OmidAccessMode" for example does.

Thanks,

Dejan

[Arnaud Leyder]

Hi,

I just sent the IMA team a screen recording of the issue.

Thanks

Arnaud

[Zacharie Taifour]

Hello, 

I can reproduce aswell when following the instructions in https://developers.google.com/interactive-media-ads/docs/sdks/html5/client-side/omsdk?hl=en#setting_access_mode_rules_for_a_request
I didn't find any OmidVerificationVendor properties neither.

Thanks,
Zacharie

[IMA SDK]

Hello Arnaud,

 

Thank you for responding back to us.

 

Would you be able to confirm if the same behavior is reproducible in one of our sample apps? I ask this as the VSI is meant for testing Ad Tags only and might not reflect all the features the SDK have. Upon confirmation, we will raise this to our team for further investigation.

 

@Zacharie & @Dejan,  thank you for chiming in, if you can confirm also the above ask it will be a great help to us.

Regards,

[Arnaud Leyder]

Hi,

Yes it can be reproduced anywhere the Google IMA JavaScript library is loaded.

Thanks

Arnaud

[IMA SDK]

Hi Arnaud,

I work along with Michael. Thank you for getting back to us.

I've checked our sample app, and can confirm the reported issue on my end as well. That said, I'll raise this (including the reports and discussion thus far) to the rest of the team for further triage. I'll update this thread the soonest they provide their feedback.

Regards,

Teejay Wennie Pimentel IMA SDK Team

ref:_00D1U1174p._5004Q2TOJCw:ref

[IMA SDK]

Hello Arnaud,

 

Hope you are doing well.

 

Our team responded back to us and confirmed that the fixed has been released for this issue. Please update to the latest version of the SDK for it to reflect on your end.

 

Let us know should you still encounter the same.

Regards,

[Arnaud Leyder]

Hi,

Thanks the issue is resolved now.

Arnaud