Success! Looks like we've fixed this one. According to our records the fix was applied for
sencha ant production build does not work for Ext JS apps
I installed 181 and created a new app (using 4.1.2a sdk)
Then, I went to the c:\projects\TestApp folder and ran
sencha generate app TestApp c:\projects\TestApp
and got this response:
sencha ant production build
If I use the old command
Sencha Cmd v22.214.171.124
[ERROR] Target "production" does not exist in the project "@@@".
it doesn't give me an error, but it also doesn't result in a production folder under the build folder; just a folder name TestApp. The only files that get copied to the build\TestApp folder are index.html and all-classes.js.
sencha app build production
Am I missing a step?
Thanks for the report! I have opened a bug in our bug tracker.
The different environment options (e.g., "production") are still touch-specific in their handling, but we must have missed adding "no op" targets for them in the Ext JS side to allow the commands to execute.
"sencha ant build" should work for both frameworks using the default environment for Sencha Touch.
I also transplanted your post from its original location on the announcement thread. Sorry for any confusion on that but we cannot link individual posts from a thread to our bug tracker.
Now I've dug down into it I think my problem here:
Is the same. I managed to discover your workaround during discovery however this doesn't solve my base problem which is that a testing build appears to be impossible. Is there a workaround to disable compression on an Ext JS build?