Qlik-embed shows no content but no error

[vlian]

Hi we are encountering an issue here. We are using qlik-embed and it successfully injects some html elements (qmfe and iframe), but does not render any content. The iframe it inserted is empty (see screenshot). There was no errors or other messages in the console so don't really have much to troubleshoot.

The html for the embed component is:

      <qlik-embed

        ui="classic/app"

        app-id="c95adbee-a89e-41d8-b06f-d7492527814b"

        sheet-id="f927b2dd-d550-4239-b1ed-d56681fea1cc"

        theme="fraedom"

      ></qlik-embed>

We are trying to use the classic/app UI. The app id and sheet id we got is working in qlik sense (see second screenshot from qlik hub)

 

[alex_colombo]

Hey @vlian which Qlik Sense on prem version are you using? Could you please inspect browser developer tool and see if websocket connection has been established correctly? Which authentication are you using?

[vlian]

Hi @alex_colombo , thanks for your response. We are on Qlik Sense May 2024 - 14.187.4, as I understand qlik-embed is only available from May 2024 onwards.

A little bit of context, we used to be using Capability API via RequireJS, and now we are trying to migrate to qlik-embed. 

Authentication is done via a session solution and a virtual proxy, I can see from the developer tools that a cookie X-Qlik-Session-jwt was successfully stored.

In our old RequireJS setup, the WebSocket connection was opened and traffic can be found once I call qlik.openApp(appId)... see screenshots below.

However, I cannot seem to find the websocket connection with qlik-embed when inspecting developer tools, even when the WebSocket connection has been established.

Based on this, I think our authentication is fine, just for some reason qlik-embed is not working with the opened socket? Any guidance would be appreciated. Thanks!

[vlian]

and FYI this is how we open the websocket connection:

[alex_colombo · Accepted solution]

I'm able to reproduce the issue on my env, please open a support case, this is a bug on "classic/app". If you try to use "analytics/chart" should work.