Thank you for reporting this bug. We will make it our priority to review this report.
2.2.2 Build 971 - unable to build native app and build is always using packager.json
Just updated and experiencing that the native build is always using packager.json. Is the packaging changed in this version? Or sending different commands to Sencha Cmd? Underneath a report.
Architect Build tested:
- 2.2.1 Build: 951
- 2.2.2 Build: 971
Steps to reproduce the problem:
- Building a project always uses "packager.json", also I am unable to get a package build anymore compared to Sencha Architect 2.2.1.
We have a configuration for Android, Android_dev, iOS, iOS_dev etc.
In Sencha Architect 2.2.1 I have build a native app like this:
The result that was expected:
- run "sencha app build native" command line from ./[project], output is ./[project]/build
- go to Sencha Architect, press "Package", go to "Package settings" and select configuration file and press "Build"
- input is configured to: ./[project]/build/package
- output is configured to go to a separate build folder per config file fe. ./[project]/../build/ios for iOS.json or ./[project]/../build/ios_dev for iOS_dev.json
The result that occurs instead:
- A signed *.app or *.apk file in ./[project]/build/[..], fe. ./[project]/../build/ios/myapp.app for iOS.json or ./[project]/../build/ios_dev/myapp.app for iOS_dev.json
- While "iOS.json" is selected, pressing "Build" from Sencha Architect runs "sencha app build native" in a terminal window using packager.json.
- No *.app is created in ./[project]/build/[..]
- Maybe I have to use a different build process? However I cannot find another working native packaging process in the documentation.
- Using "sencha app package run [configFile.json]" in ./[project] builds and signs the package as expected
Last edited by rmsint; 1 May 2013 at 6:36 AM.
Reason: Further debugging
First yes we have changed the way we do package build and package simulate
build: sencha app build native
sim: sencha app build -r native
Both of these commands do in fact use packager.json and cannot be assigned another json file.
For your setup you can simply use
sencha app package android.json
This will have Architect doing the first part (that you were doing at the cmd line before)
Then unfortunately you'll have to run the 2nd part (that Architect did for you before)
The reason for the change:
Many customers were trying to simulate and build using the local app directory and never doing a build first. This was very problematic as you yourself learned and resorted to a build of your own.
This change helps the less advanced user, that uses just one packager.json file and does the build and package in 1 step.
We are currently working on a much more powerful and simple build system that will allow you to have targets and different settings for each target. Example targets: build for android, simulate for iOS, build for web, etc ...
This will on the back end create a new packager.json file that Cmd can read depending on the target you chose and the settings you enter per target.
Thanks for your quick response and good to hear I was on the right track. Looking forward to see the future build system.