Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
tdudley0302
Contributor
Contributor

Qlik Custom Theme iframe Same Origin Policy Error

Hey All,

I'm having a problem in which I've created a custom theme for my Qlik Sense app and am running into Same Origin Policy issues when trying to display a single configuration through an iframe.  Here is the exact error:

Error: Blocked a frame with origin "https://qlik.xxxxxxxx.com" from accessing a cross-origin frame.

    at Object.o.getTenantId (qlik.xxxxxxxx.com/vp/resources/js/single.js?1522774745642:1)

    at Object.i [as getTenantIdUrlParameter] (qlik.xxxxxxxx.com/vp/resources/js/single.js?1522774745642:1)

    at Object.c.injectStyleNode (qlik.xxxxxxxx.com/vp/resources/js/single.js?1522774745642:1)

    at qlik.xxxxxxxx.com/vp/resources/js/single.js?1522774745642:1

    at Array.forEach (<anonymous>)

    at Object.c.injectExtraStyleNodes (qlik.xxxxxxxx.com/vp/resources/js/single.js?1522774745642:1)

    at qlik.xxxxxxxx.com/vp/resources/js/single.js?1522774745642:1

    at a (require.js:1)

    at require.js:1

    at p.$eval (require.js:1)

Has anyone else ran into this issue and if so how do you solve it?  I tried adding Access-Control-Allow-Origin: * to the virtual proxy response headers but that didnt make a difference. 

Any help would be greatly appreciated!

1 Solution

Accepted Solutions
tdudley0302
Contributor
Contributor
Author

If anyone else comes across this same problem, this appears to have been due to a bug in the April 2018 release of Qlik Sense.  Updating Qlik Sense to April 2018 Patch 1 fixed this problem for me.

View solution in original post

1 Reply
tdudley0302
Contributor
Contributor
Author

If anyone else comes across this same problem, this appears to have been due to a bug in the April 2018 release of Qlik Sense.  Updating Qlik Sense to April 2018 Patch 1 fixed this problem for me.