# ERR\_BLOCKED\_BY\_RESPONSE error on webos 22 TV

**URL:** <https://forum.webostv.developer.lge.com/t/err-blocked-by-response-error-on-webos-22-tv/4722>\
**Category:** Web App Development\
**Created:** [December 14, 2023, 8:54am UTC](https://forum.webostv.developer.lge.com/t/err-blocked-by-response-error-on-webos-22-tv/4722 "2023-12-14T08:54:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![user2220](https://avatars.discourse-cdn.com/v4/letter/u/dfb087/32.png) [@user2220](https://forum.webostv.developer.lge.com/u/user2220)\
**Post date:** [December 14, 2023, 8:54am UTC](https://forum.webostv.developer.lge.com/t/err-blocked-by-response-error-on-webos-22-tv/4722/1 "2023-12-14T08:54:58Z")

</div>

We are developing an app using a webos 22-based simulator and real equipment. When calling our internal backend API, no error occurs in the simulator, but an error occurs on the actual TV equipment. The error details are as follows.

 ![스크린샷 2023-12-14 오후 5.51.30](https://canada1.discourse-cdn.com/flex030/uploads/webostv/original/1X/945c9159a5bd268aa8cbf6b10ca7fb18cc89a24f.png)  
Also, the error does not occur when testing on a webos 23 physical TV with the same ipk file.  
Below are the header details for the request.  
 ![image](https://canada1.discourse-cdn.com/flex030/uploads/webostv/original/1X/a1e14c118f6b0cdf12ee366494575349279e582d.png)  
If the request is successfully performed, sec-fetch-mode in the request header is set to cors.

---

<div class="post-metadata">

**Author:** ![narae0.kim](https://avatars.discourse-cdn.com/v4/letter/n/87869e/32.png) [@narae0.kim](https://forum.webostv.developer.lge.com/u/narae0.kim)\
**Post date:** [December 20, 2023, 12:43am UTC](https://forum.webostv.developer.lge.com/t/err-blocked-by-response-error-on-webos-22-tv/4722/2 "2023-12-20T00:43:19Z")

</div>

Please share with us the following at [developer@lge.com](mailto:developer@lge.com).

- Your app .ipk file
- Steps to reproduce the issue

And the following information of the webOS TV 22 and 23 are also required. (You can check this in the Settings \> General \> About This TV.)

- TV model name:
- TV software version:
- webOS TV version: (This can be found when you click the TV model name in the About This TV menu.)
- Region:

---

<div class="post-metadata">

**Author:** ![AboodRaj](https://avatars.discourse-cdn.com/v4/letter/a/6bbea6/32.png) [@AboodRaj](https://forum.webostv.developer.lge.com/u/AboodRaj)\
**Post date:** [June 17, 2026, 11:44pm UTC](https://forum.webostv.developer.lge.com/t/err-blocked-by-response-error-on-webos-22-tv/4722/3 "2026-06-17T23:44:38Z")

</div>

I have encountered this issue, the reason the issue occurs is because the response header coming from the server has a cross-origin-resource-policy of “same-origin”,  
If you have the ability to change the response header to “cross-origin” would fix the issue based on my experience,  
what i did, to prevent setting CORP to cross-origin to all response,  
I created a service that acts as a proxy to the TV app where i set the Origin to a string value, the backend recognizes to set the CORP to “cross-origin” programmatically