One-Line Summary: A ReferenceError for URLSearchParams occurs inside the IMA SDK's bridge iframe, causing widespread ad failures on key living room platforms including Xbox, PlayStation, Tizen, and WebOS.
When an ad is requested using the latest version of the IMA SDK, the SDK's bridge iframe (bridge{version}_pl.html) executes code that calls URLSearchParams. This API is not natively supported on many modern console and smart TV web environments. As a result, a fatal ReferenceError: Can't find variable: URLSearchParams is thrown.
This suggests that the isolated iframe environment for the ad creative does not include the necessary polyfill for URLSearchParams, breaking the ad rendering process for a significant portion of CTV (Connected TV) traffic.
SDK: Google IMA SDK for HTML5
Version: Latest (as of September 2025)
Platforms Affected: This is not limited to older desktop browsers. We have confirmed this error occurs on:
Xbox (all models)
PlayStation (PS4, PS5)
Tizen 3.0
WebOS 3.0
Other similar WebView-based environments.
Integrate the latest version of the Google IMA SDK on a webpage.
Load the page and request a VAST ad on any of the listed console or smart TV platforms.
Observe the developer console (via remote debugging).
The ad should load and play correctly. The IMA SDK's internal iframe should be self-contained and provide any necessary polyfills to ensure compatibility across all its supported devices, including major consoles and smart TVs.
A ReferenceError is thrown from within the SDK's bridge iframe, preventing the ad from loading. This critical bug blocks monetization on key living room devices.
Suggested Fix: Please include a polyfill for URLSearchParams within the bridge iframe's context to ensure backward compatibility and restore functionality on affected platforms.
Hi,
Thank you for contacting the IMA SDK Support team.
As per the documentation, the IMA SDK supports specific platforms and compatibility requirements. For further investigation, could you please provide the VAST tag and a screen recording capturing the issue?
Additionally, we recommend use the latest version of the SDK to ensure full compatibility and access to the latest fixes.
Please continue using this thread instead of creating multiple threads, so we can focus on the investigation more effectively.
Kindly provide the requested details via Reply privately to the author option.
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=500Ht00001u7yPTIAY&entry.80707362=003343252. 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.
![]() |
IMA SDK Team |
[2025-10-01 12:29:19Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01u7yPT:ref" (ADR-00334325)