[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