IMA SDK for iOS overwrites `url` VAST parameter (BUG)

[Amitai Blickstein]

Is this bug a known issue? Are there workarounds, or other guidance you can give? 

Thank you,

Amitai Blickstein

iOS SDK Engineer

JWPlayer

---

Summary

The IMA SDK for iOS is overwriting the url VAST tag parameter with a generic default.

Reproduction

This can be seen in the IMA VSI iOS app, such as adding the example URL param (&url=https%3A%2F%2Fwww.videoad.com%2Fgolf.html) to the Single Skippable Linear sample ad tag (from the sample tags page):

https://pubads.g.doubleclick.net/gampad/ads?iu=/21775744923/external/single_preroll_skippable&sz=640x480&ciu_szs=300x250%2C728x90&gdfp_req=1&output=vast&unviewed_position_start=1&env=vp&impl=s&correlator=&url=https%3A%2F%2Fwww.videoad.com%2Fgolf.html

Expected Result

The outgoing request (captured by Charles Proxy or other network traffic monitor) should have the URL query passed through, &url=https%3A%2F%2Fwww.videoad.com%2Fgolf.html

Actual Result

The outgoing request is below in full, but note it has URL set to com.google.IMAMobileVSI.adsenseformobileapps.com/

which is the preferred default/fallback for this required parameter mentioned in the docs linked above in the first link.

---

https://pubads.g.doubleclick.net/gampad/ads?iu=%2F21775744923%2Fexternal%2Fsingle_preroll_skippable&sz=640x480&ciu_szs=300x250%2C728x90&gdfp_req=1&output=xml_vast4&unviewed_position_start=1&env=vp&correlator=4480939437135620&url=com.google.IMAMobileVSI.adsenseformobileapps.com%2F&vpa=click&sdkv=h.3.365.2%2Fn.ios.3.19.2%2Fcom.google.IMAMobileVSI&osd=2&frm=0&vis=1&sdr=1&hl=en&attmas=not_determined&idtype=idfa&rdid=00000000-0000-0000-0000-000000000000&paid=5E292E65-244F-4658-8563-45360AECC93B&paid2=379D59ED-12D4-407C-B0C6-2D59FF2264F9&paopt=0&ms=gQAL5kQL6KG6HsiDSeLsJulI1ow1yH5iDlgqUlPpLDY5r2L3o4bFYjSSdH2ETpeqFZ72dqhpBCGYC3U511iO9LpOj-emxvlZEWviQWY7qlBi9bUwANwkKilszcEUnGeyJj31yxRtdugL-Og8K26WmZdwRBenBl-KLiOYHq1hPZkQYNIWl3gJr2u82wJ-VTbE4SyKCH4962AWbvQ948Q6LfoVLKeZgP-e17EUKmkMxu-H2rfjoYhxLYvwy5wYmvxEgrRUqwHs8wQL8cUIB-dX27a7Q8LoGDbFLHRRDEWD2uglpecRga9MdSZxJzH-64JXdeI9334xIGEXeRr3ltZ3LQ&is_amp=0&js=ima-ios.3.19.2&an=com.google.IMAMobileVSI&u_so=l&ctv=0&sdki=445&ptt=20&sdk_apis=7%2C8&omid_p=Google1%2Fios.3.19.2&sid=E285C054-821C-4A09-9BA8-1190DE83695A&nel=0&eid=44772139%2C44777649%2C44781409%2C44781753%2C44782991%2C44788275%2C44793913&dlt=1694013364196&idt=35&dt=1694013453470&scor=4395419990898805&submodel=iPhone13%2C3

[IMA SDK]

Hello,

Welcome to IMA SDK Support team. Thank you for reaching out to us.

Can you please confirm if you are using the iOS SDK or is this an HTML5 SDK in webview on a iOS app? Moreover, have you replicate the same issue in one of our sample apps?

• HTML5 SDK sample app - https://github.com/googleads/googleads-ima-html5/releases
• iOS SDK sample app - https://github.com/googleads/googleads-ima-ios

If not, can you share to us instead the sample code implementation of your app where the issue is reproducible so we can test on our end? It would be best if you can also share to us the charles log and steps to reproduce the issue so we can expedite the investigation process.

If the file(s) you are looking to share are less than 25mb in total you can attach them to this case on your next reply. If you are having trouble attaching your file to this case or if your file(s) are larger than 25mb, you can share your files with me by performing the following steps:

1. Navigate to

https://docs.google.com/forms/d/e/1FAIpQLSfkAiXMeYP-fw1W3Z-tT9uwmATEKO5X6S-th0gR2ezdKaaqfg/viewform?usp=pp_url&entry.400550049=IMA+SDK&entry.460850823=5004Q00002oirmSQAQ&entry.80707362=00197217

2. Fill out all fields, and attach your file(s).

3. Please reply back on this thread when you have uploaded your file(s). Please do not share this link.

 

This message is in relation to case "ref:_00D1U1174p._5004Q2oirmS:ref"

Thanks,
 

IMA SDK Team

[Amitai Blickstein]

I reproduced this on the IMA SDK for iOS VSI app. To reproduce:

1. Open the VSI App

2. Tap the "edit" right bar button item.

3. Tap the "Ad Tag URL" table view cell

4. Append &url=https%3A%2F%2Fwww.videoad.com%2Fgolf.html to the end of the tag.

5. Tap "Back"

6. Tap "Done"

7. Activate Charles or other traffic monitor.

8. Tap "Start".

Does this suffice? 

Thanks!

[IMA SDK]

Hi Amitai,

Thank you for providing more information.

I understand that you were able to reproduce this behavior when using the VSI app. Please note that as stated in the document you referred to as well, for apps, if it is not possible to set this parameter to a variable URL value, it's recommended that it be set with the following pattern: [ url=<app/bundleid>.adsenseformobileapps.com ]. Kindly check also the recommended usage for the description_url. The description_url value must be URL-encoded for web page video players and CTV/OTT devices and non-encoded for mobile in-app video players. Additionally, I also suggest that you test your modified VAST ad tag URL using the VAST suite inspector. 

[Amitai Blickstein]

Hello Team,

Thank you for getting back to me. Are you saying that the SDK determined it "not possible " because I did not set the description_url in my test? 

I found that making sure to use absolute paths rather than relative paths resolved the issue, and the SDK is behaving as expected for a real tag (but, as above, not with my contrived test using a sample tag + usage example). So, aside from answering my curiosity above, this issue is resolved, with my thanks for your quick reply.

Best,

Amitai

[IMA SDK]

Hello Amitai,

Thank you for responding back. Glad that the issue is resolved. We can only recommend to follow the suggested usage in this documentation (https://support.google.com/admanager/answer/10660756?hl=en&ref_topic=10684636&sjid=8412471390060646439-NA#url). There might be differences from using a sample VAST tag from a real tag. Since the sample tag's  main purpose is just for ad request behavior and display checking of your implementation. Do not hesitate to come back to us if you have further questions on this matter. Otherwise, we suggest that you open up a new thread if you encounter another issue.