topic Re: "Not Connected" popup in Mashup when reopening a closed app in Integration, Extension & APIs

"Not Connected" popup in Mashup when reopening a closed app

alastairmcdonald — Wed, 17 Oct 2018 13:53:17 GMT

I am working on a mashup that has navigation betwene two separate apps.

I load the first app and render my visualisations as necessary then on the user clicking a navigation button i close the first app and open a second before rendering. this works fine however when i try to navigate back to the first app and reopen the connection i get a not connected pop up.

Weirdly the app does open and all the visualisations are displayed correctly.

I read a post indicating that it could be related to not closing the models that are created when using the app.getObject method

so i tried doing the following when getting the objects:

app.getObject(portal.visualisations,portal.visualisations).then(function(model) {

models.push(model);

});

and before closing the app:

angular.forEach(models, function(value){

value.close();

});

but i still get the "Not Connected" message when reopening the previosuly closed app connection.

Does anyone have any idea what i may have missed?

Message was edited by: Alastair McDonald spelling punctuation and grammmar

Re: "Not Connected" popup in Mashup when reopening a closed app

ErikWetterberg — Thu, 18 Oct 2018 03:40:58 GMT

HI Alastair,

this sounds like a bug. I assume that you reopen by calling Qlik.openApp again, which should create a new web socket. You would then need to call getObject again using the new app. Try checking the web socket traffic and see where the error message comes from.

Erik Wetterberg

‌https://extendingqlik.upper88.com/

Re: "Not Connected" popup in Mashup when reopening a closed app

alastairmcdonald — Thu, 18 Oct 2018 12:01:18 GMT

Hi Erik,

I am looking at the web socket traffic in chrome dev tools and I can still see the original web scoket is open even after calling close() on the app. the new connection is also listed as pending.

Re: "Not Connected" popup in Mashup when reopening a closed app

ErikWetterberg — Thu, 18 Oct 2018 12:10:02 GMT

Hi,

so that is a bug, according to the documentation app.close() should close the websocket:

https://help.qlik.com/en-US/sense-developer/September2018/Subsystems/APIs/Content/Sense_ClientAPIs/CapabilityAPIs/AppAPI…

You probably should report it. What Qlik Sense version are you using?

Erik Wetterberg

https://extendingqlik.upper88.com/

Re: "Not Connected" popup in Mashup when reopening a closed app

alastairmcdonald — Thu, 18 Oct 2018 12:24:48 GMT

I'm using Qlik Sense Enterprise June 2018.

I'll have a word with technical support see if they can help.

Re: "Not Connected" popup in Mashup when reopening a closed app

alastairmcdonald — Thu, 18 Oct 2018 12:36:32 GMT

on support.qlik.com it lists the following information

Description

What information is available on the compatibility of Qlik Sense with Angular?

Environments:

Qlik Sense Enterprise, all versions

Resolution

Qlik Sense APIs were developed in a particular version of Angular, which is discoverable from the Hub in About > Third-party software as described on the help site, Using AngularJS in your mashup.

Here are a few examples:

Qlik Sense Version	AngularJS Dependency
February 2018 Patch 1	1.5.0
June 2018	1.6.9

But when I log angular.version into the console i get the following:

{full: "1.5.8", major: 1, minor: 5, dot: 8, codeName: "arbitrary-fallbacks"}
1. codeName: "arbitrary-fallbacks"
2. dot: 8
3. full: "1.5.8"
4. major: 1
5. minor: 5
6. __proto__: Object

Have i missed something or do I need to upgrade angular on my qlik server somehow?

Re: "Not Connected" popup in Mashuop when reopening a closed app

alastairmcdonald — Thu, 18 Oct 2018 14:29:23 GMT

checking the require.js files at ../assets/external/requirejs/require.js shows that it is in fact loading angular 1.5.8...

I'm running a repair on my Qlik Sense services while I wait for support to reply to my ticket.

Re: "Not Connected" popup in Mashuop when reopening a closed app

alastairmcdonald — Thu, 18 Oct 2018 17:26:15 GMT

I've upgraded to Septmber 2018 which does have 1.6.9 in its require.js but the error is still there so probably unrelated

Re: "Not Connected" popup in Mashup when reopening a closed app

ErikWetterberg — Tue, 23 Oct 2018 06:19:13 GMT

Hi,

Looks like your first and fourth web socket are connections to the same app. Are you sure that you close the first one before opening the second one? Also looks like you are using the identity parameter, do you use the same identity for all connections or different ones? What happens if you remove the identity parameter, do you still get the same error?

Also looks like you have a open global web socket. What do you need that for? You might not need it, since you can use app.global instead (which reuses the app web socket instead of opening a new one).

Erik Wetterberg

https://extendingqlik.upper88.com/

Re: "Not Connected" popup in Mashup when reopening a closed app

alastairmcdonald — Thu, 25 Oct 2018 09:24:20 GMT

Hi Erik,

thanks for taking a look, I am not using app.global but will amend the code to see if that makes any difference.

I believe i am closing the first web socket to the app before opening the second as i call the close method on the app and this is done asynchronously using promises.

Re: "Not Connected" popup in Mashup when reopening a closed app

alastairmcdonald — Thu, 25 Oct 2018 09:37:28 GMT

I've also tried with and without an idnetity parameter and get the smae thing happening

Re: "Not Connected" popup in Mashup when reopening a closed app

alastairmcdonald — Fri, 30 Nov 2018 11:50:24 GMT

Okay so i have narrowed it down.

i followed this post: https://community.qlik.com/t5/Qlik-Sense-Integration/Qlik-Sense-Mashup-Unloading-Objects-from-Memory/td-p/3825

and was able to dispose of objects successfuly however i cannot use this for the CurrentSelections object.

When i add the current selections object back into my code using getObject i get the error.

does anyone know how to do effective cleanup / disposing of the selections bar? generated by getObject?

Re: "Not Connected" popup in Mashup when reopening a closed app

ErikWetterberg — Fri, 30 Nov 2018 12:06:00 GMT

Hi,

internally the selections bar is different from the other objects, so it might very well work differently. Why do you need to close it? Why not just keep it, and use the show method if you need it somewhere else. Or just keep it displayed all the time.

Re: "Not Connected" popup in Mashup when reopening a closed app

alastairmcdonald — Fri, 30 Nov 2018 12:10:52 GMT

the problem is i am flipping between multiple QS apps in my mashup and when i return to a previously visited app the selection bar stops working. i had hoped by attempting to close it correctly i could reopen it when revisiting an app a second time.

obviously there is a separate selection bar for each app and i am not trying to pass selections betweeen them simply reload the selection bar each time that corresponds to the app the mashup is based on

Re: "Not Connected" popup in Mashup when reopening a closed app

alastairmcdonald — Fri, 30 Nov 2018 18:27:13 GMT

I solved it thanks to your help Erik,

i now have my getter method check for the object and if it exists just use object.show the second time. this seems to work without me needing to close the connection to the app or close the visualisations when navigatiing between apps.

Thank you.