Common reasons for extension to break after upgrade

[mgranillo]

What are some common reasons an extension might break after an upgrade?  I'm asking because we have some extensions that are no longer supported and can't update to the latest version.  In several cases the extension doesn't throw an error in the console log but shows empty white space in the app.

[ErikWetterberg]

Hi,

a common reason is that the extension uses an undocumented method or module that has been removed. I recently helped a customer with a case where the reason was a method called inClient() that seems to no longer exist in September 2019.

The Qlik Sense client catches errors in extensions and silently ignores them. That might be why you don’t see any error in the console. You could try and set the ‘break on caught exceptions’ flag and see what happens. But that probably will give you a lot of errors that are no problem too.

[ajaykakkar93]

Hi,

Can yo share which extensions are causing the issue, i might be able to help.

[mgranillo]

There's not one particular extension I'm trying to fix but here's a few i can recall having problems.

"Document Chaining"

"ClimberKPI" <-- removed but using old version

"xTableBox"

[ajaykakkar93]

There can be some JavaScript that might be causing the issue before the object is been created in UI. If you are still facing the issue I suggest you attach the extension as zip & I'll look into it

[mgranillo]

Thanks for being willing to look at the code.  Here's one from the garden.  This one does show an error.

[mgranillo]

Here's another one

[ajaykakkar93]

Reason for breakdown is "core.models/engine" in define it couldnt be found

https://community.qlik.com/t5/Qlik-Sense-Integration/Is-GetTablesAndKeys-broken/m-p/992502

If any body knows how to fix this, it will be a great learning for us.