[IMA SDK HTML5] Regression in IMA SDK 3.725.0+ – Ads not loading in Edge 44 (EdgeHTML 18) with long page URLs (~1400B)
Jani Plesnicar
Hi everyone,
We’ve encountered a regression in the IMA HTML5 SDK starting with version 3.725.0 (and continuing in later versions).
When running under Edge 44 (EdgeHTML 18), ad loading silently fails when the page URL exceeds roughly 1400 bytes.
Summary
Environment: Edge 44 (EdgeHTML 18) (UWP WebView1)
Last working version: 3.724.0
Broken versions: 3.725.0 and newer
Issue: adsLoader.requestAds(adsRequest) fails silently — no events fired, no errors logged.
URL length: around 1400 bytes (typically due to long query parameters)
Details
After initializing the AdsLoader and calling:
`adsLoader.requestAds(adsRequest);`
...nothing happens, no google.ima.AdsManagerLoadedEvent.Type.ADS_MANAGER_LOADED or
google.ima.AdErrorEvent.Type.AD_ERROR events are triggered.
There are no console errors, no CORS failures, and no network requests initiated for ad fetching.
This only occurs when the page URL exceeds roughly 1400 bytes.
If we shorten the URL, or downgrade to 3.724.0, ad loading works normally again.
We suspect this may be related to the SDK’s internal use of URLSearchParams, introduced around version 3.722.0.
Temporary workaround
We’ve been able to restore functionality by:
- history.replaceState(null, '', '/page.html');
- adsRequest.pageUrl = '<actual full page URL>';
Impact
This issue prevents ad playback entirely in Edge 44 (EdgeHTML 18) when page URLs are long, which can also affect tracking and pixel loading as combined URLs may exceed 2KB.
Request
Could you please:
- Confirm whether the change involving URLSearchParams introduced this regression?
- Consider restoring compatibility for EdgeHTML environments, or provide a supported workaround.
Thanks,
Jani
Süleyman Temir temir5org
--
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+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ima-sdk/63ff7419-65c6-4e0e-8d61-47442d85d3efn%40googlegroups.com.
IMA SDK
I will raise this issue with our wider team for further review and will update you as soon as I have any new information.Meanwhile, your patience is important.
Thanks,
 |
IMA SDK Team |
Feedback
How was our support today?
[2025-11-10 15:07:01Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vSVlT:ref" (ADR-00338320)
IMA SDK
Thanks,
|
|
||||
Feedback
How was our support today?
[2025-11-13 10:47:00Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vSVlT:ref" (ADR-00338320)
Jani Plesnicar
We are rendering ads using IMA SDK inside of UWP WebView 1 - which uses EdgeHTML as rendering engine, which is a very similar environment to what most of CTV uses. The Legacy Microsoft Edge was just used as a surrogate example as it is easier to test this in an actual browser than inside of WebView. We are limited to this environment.
The simplest way to test this behaviour is by loading video suite inspector (https://googleads.github.io/googleads-ima-html5/vsi/) with added fake query string params
Use VM with Edge 44 (aka EdgeHTML 18), or BrowserStack with Edge 18.
- Add random query parameters at least of 1000 characters to the end of the video suite inspector (eg.: https://googleads.github.io/googleads-ima-html5/vsi/?test=JGrYdhpTUt4pk8eFXWqKPzVrff3F1Z8ReeF52NCHNNWhSV1YKE4TCJFyjC0d4KvD6P1anxjDuM7KmQyVt3Yqr7QyQrxXcQJa9kcMGYxBSk59JNu2TfL8WSDeyzhgpF56dRTyuicx0DG6wBiqxauLytrYcuYNr3k6X78WpxV8PceS89RKhQRB9HthnFywcSb8iWL8hpiWyyytXXR38atkcHmxRUVtWT0ya8weTRiyZ7Da3TqU4QU1eX9hdGr1LuPhug5bLKXR9HNRfniEeWXfQF203HKCpAGKS0SKvtd5A9DhaMrepicMuKupTc1CfNTd3iCmj3MVRRra5j5ec2hZjjFtcLfQgvTCmphJafKLDxw1wS4h5n4VMAKvCcNyuYXkCMfifbjtp6nXNxVKVz49EizXwXvjTuVJrk6VaNZ41hyDmWA9nRrGencgP7U3jrE1D3CcQ9VqLgNb7r9BNNwYjnP5GFRP4jHcV0jq39rYMPvL6B4m7bjS0zVPvM8N2LbKdJDCMtRL4NGxyKSrgJdXmmxTcwW2YdgCe7W6zBT6CBxaKZiKFqSRDgDPnD6m8AB4MmuZZaQVNfWQQWyeyVyxDU9Q9unCR2mYuU3NV5WYfVpgbWqbhkfp789SSM1bfrAju9X6XjYj0X9kbu536WAyufC8HKdXgh6Qt2q9DPBzLLMxniBxKzc8B37kaZ9JQTDxKBAtNAmR9ywYCLcjiUZvcWKzYXMTXj5TrPhWSf7NtmGUjbcmEav2ViRE4pGZPWn5qF9A3tM1ZDKeR8XrdUhKNvaTTMmggS5iZEptvXGSAiaaBgCwAgNvi3q4cmbGRAizyXSvrBy5mjXbieXVFeWwA86Hb9BxWVCS5nS345KruWBpFfPZ267WRGx5ifRALutCExMDv0Hkc4aw9DiaVE5hzN9i7FpXSi4pXxJV8ZGTcZtUXcwWJWYEQgnjgA9Mk8LhZgWizmLDXgNW9AmTXcQ7xc90bPYBVKKnym5SF2fy)
- Use Sample VAST tag or any other that works with normal length URL
- Clicking Test Ad won't do anything (bridge doesn't load) - the SDK doesn't error nor report ad manager loaded event. Before version 3.725.0 this worked normally.
The issue is reproducible in a sample project via localhost url. The same way it was is reproducible with video suite inspector.
Would this suffice as a sample?
Best Regards,
Jani
Hi Jani,
Thank you for contacting the IMA SDK Support team.
According to the official IMA HTML5 SDK compatibility guidelines, supported desktop browsers include Chrome, Firefox, Safari, Edge, and Opera. We recommend upgrading to the latest Microsoft Edge and retesting your integration.
To help us investigate this issue further, please confirm whether the problem also occurs in our sample project. Additionally, share the following details so we can perform a deeper analysis:
Your sample project where the issue reproducible
Charles log
VAST tag
A screen recording demonstrating the issue
These details will allow us to reproduce and diagnose the issue more effectively.
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:
2. Fill out all fields, and attach your file(s).
3. Please reply back to this thread when you have uploaded your file(s). Please do not share this link.
Thanks,
IMA SDK Team
Feedback
How was our support today?
[2025-11-03 23:46:23Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vSVlT:ref" (ADR-00338320)
