Thank you for reporting this bug. We will make it our priority to review this report.
-
Ext JS Premium Member
SA 4.1 Theme Error
Hi all,
in SA, after add a new theme into project,
build make an error: CMD packaged failed!
Any ideas?
Thanks,
Luca
-
Hi
Could you please describe how you add new theme package please?
thank you
-
Ext JS Premium Member

Originally Posted by
petr.vecera
Hi
Could you please describe how you add new theme package please?
thank you
Yes.
1) Open SA
2) New BLANK Modern Project
3) Automatically Triton Theme appear on inspector
4) Add Panel Component
5) Save Project
6) Error appear
-
Ext JS Premium Member
Same error in SA 4.2.1:
- without Panel Component
- ExtJs 6.5 Modern
-
Yeah it seems that something become broken on your computer. Please quit SA, remove folder extracted and start SA again.
It should be located here:
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
-
Ext JS Premium Member
Nothing change,
1) deleted folder /Users/LucaFerrarese/Library/Application Support/Sencha/Sencha Architect 4.0
2) start SA 4.1.2.188
3) activation required... ok
4) new project modern Extjs 6.2
5) save project
CMD theme package failed!
-
Ext JS Premium Member
In this video i share the problem for a fast solution:
https://vimeo.com/226164474
Please, help me!
-
Ext JS Premium Member
workspace.json will help?
{
/**
* An array of the paths to all the applications present in this workspace
*/
"apps": [
"_App/zapBox",
"_App/CastelFerrarese",
"_App/ZapGrid_installatore",
"_App/zapBox_gold",
"_App/TO/T12",
"packages/local/theme-triton-28541686-11e4-43de-a0d3-7201a68dcb56/.sencha/temp/Themer"
],
/**
* An object containing key value pair framework descriptors.
*
* The value can be a string or an object containing at least one of "dir" or "pkg",
* where "dir" can be a filesystem path to the framework sources and "pkg" can be a
* package name. For example:
*
* "frameworks": {
* "ext": "ext",
* "ext-x": "/absolute/path/to/ext",
* "ext-y": {
* "source": "../relative/path/to/ext",
* "path": "ext"
* },
* "ext-z": {
* "package": "[email protected]",
* "path": "ext-n.n.n"
* },
* "touch": "touch"
* }
*
*/
"frameworks": {
"ext621": {
"path":"ext621",
"version":"6.2.1.167"
},
"ext": {
"path":"ext",
"version":"6.2.1.167"
}
},
/**
* This is the folder for build outputs in the workspace.
*/
"build": {
"dir": "${workspace.dir}/build"
},
/**
* These configs determine where packages are generated and extracted to (when downloaded).
*/
"packages": {
/**
* This folder contains all local packages.
* If a comma-separated string is used as value the first path will be used as the path to generate new packages.
*/
"dir": "${workspace.dir}/packages/local,${workspace.dir}/packages",
/**
* This folder contains all extracted (remote) packages.
*/
"extract": "${workspace.dir}/packages/remote"
}
}