"Error Loading Control" after update to PowerCAT-Code-Components v1.1.41

[pnichols77]

I have PowerCAT installed as a managed solution and have upgraded this solution to the latest release previously without issue.

I have downloaded this latest release and imported it. The import reported as successfully completed and upon opening an existing app that uses these components in an editor I was presented with the expected component update prompt.

However existing and new components added to my app - even ones I have not used before - show "Error loading control" in place of the control. I have tried re-importing the solution and reloading the affected app.

I was considering removing the solution and re-adding, but im not sure what the implications of doing this would be for existing, published apps that are using the controls in this solution.

[S-GRog]

I have the same issue. Ok after importing the solution, but updating the components makes them fall in Error.
I can roll back the app and skip update and use already imported components. But if I try to add new ones that weren't in the app they have this error loading control.
I'm gonna try to import a previous version that was working.

[pnichols77]

I tried rolling back to the previous, working version but I am unable to as it will only allow the import of the same or a higher version.

[S-GRog]

I rolled backed this morning to the previous version i had installed (v1.1.37).

You need to unzip the solution and change the version number in the solution.xml and each ControlManifest.xml contained in the controls folder. I choose to do 1.1.411, zip the folder again and import the solution.

Once you edit your app, you still have to update components but for me it's just like before. Not sure if this was a good practice to do do the roll back like that.

I'll wait next version to test it out.

[pnichols77]

Not sure if anyone is actually reading this but ive also noticed that while i have version 1.1.41 showing as installed, the components themselves are reporting as being the previous version (though with the date of the latest update).

So there's either something wrong with this build, or how the update has been applied in my environment.