SA 4.2 Upgrade - Infinite Upgrading Auxiliary File

[nclemeur]

Looks like the trick for me was to first create a new project using the same framework (ExtJS 6.2.1 classic), saving, closing SA and then opening my project again. This seems to work much better but I'll need to work a bit longer with it to be sure.

[petr.vecera]

Hello guys

We are able to confirm this issue. It can happen when you upgrade to SA 4.2 and the first project you open is the project with Themer theme.

Workaround:
# Start SA 4.2
# Create new ExtJS 6.2 or 6.0 blank project ( you don't need to save it) - you should see "updating auxiliary files" quickly finish
# Now you can open any project you need

^^ if the above steps doesn't help you can also delete extracted folder before starting SA located in:

User data path - IMPORTANT: The path is still 4.0 even for SA 4.1 and 4.2
Windows
C:\Users\<user>\AppData\Local\Sencha\Sencha Architect 4.0
Mac
/Users/<user>/Library/Application Support/Sencha/Sencha Architect 4.0
Linux
~/.local/share/Sencha/Sencha Architect 4.0

We are sorry for the inconvenience caused by this.
Petr

[rcmartin]

This workaround worked for me as well after experiencing the previously described symptoms while opening an existing project (Windows 7, Ext JS 6.0,2).- thanks!

Bob

[grosst]

Hello guys

We are able to confirm this issue. It can happen when you upgrade to SA 4.2 and the first project you open is the project with Themer theme.

Workaround:
# Start SA 4.2
# Create new ExtJS 6.2 or 6.0 blank project ( you don't need to save it) - you should see "updating auxiliary files" quickly finish
# Now you can open any project you need

^^ if the above steps doesn't help you can also delete extracted folder before starting SA located in:

User data path - IMPORTANT: The path is still 4.0 even for SA 4.1 and 4.2
Windows
C:\Users\<user>\AppData\Local\Sencha\Sencha Architect 4.0
Mac
/Users/<user>/Library/Application Support/Sencha/Sencha Architect 4.0
Linux
~/.local/share/Sencha/Sencha Architect 4.0

We are sorry for the inconvenience caused by this.
Petr

You should probably also do the same with an Ext 65 project as well if you plan to upgrade. Seems the loop carries on there for me as well.

[dnoizet]

I had this problem too while upgrading an existing Ext 6.2x project to 6.5x, and the extracted folder was almost empty. I had the "upgrading auxiliary files" loop.
So I followed the following procedure.
- Killed any running instances of SenchaArchitect.exe and sencha.exe
- Reverted my project to pre-upgrade state
- Deleted the whole extracted directory and created a blank project for Ext 6.0x, 6.2x and 6.5x. This added some json and folders inside the extracted directory
- Tried to upgrade my project again. This time successfully :-)

[tlloyduk]

Hi

To fix the problem please delete the folder C:\Users\<user>\AppData\Local\Sencha\Sencha Architect 4.0\extracted
If anyone else comes across this problem please let us know about it.

Thank you
Petr

Hi Petr,

I appear to have the same problem after upgrading to Architect 4.2 and opening an existing project (nothing really to note except it does use a custom theme generated by Sencha Themer 1.1).

The steps outlined above in the workaround section do not appear to have worked for me.

After the project opens I get lots of "Removing old auxiliary files" flashing up and then eventually it gets stuck on the message: https://snag.gy/cNOEG8.jpg

I tried deleting the "extracted" folder but this didn't help and the folder was created again and it contains one file ext62-compile.zip: https://snag.gy/Bt1HeF.jpg

One thing to note is once it gets stuck on this message the memory usage for the process just seems to increase forever.

Creating a New project seems to work ok. But re-opening the existing project still fails.

Any other ideas ?

Thanks

[tlloyduk]

OK ignore me, I was creating a new 6.5 project not 6.2 - it now seems to work