It would be great if we somehow can Ant do al the signing and zipalign. How can we make this work?
If you are using Ant, you can enable release mode by using the release option with the ant command. For example, if you are running Ant from the directory containing your build.xml file, the command would look like this:
$ ant releaseBy default, the build script compiles the application APK without signing it. The output file in your project bin/ will be<your_project_name>-unsigned.apk. Because the application APK is still unsigned, you must manually sign it with your private key and then align it using zipalign. However, the Ant build script can also perform the signing and aligning for you, if you have provided the path to your keystore and the name of your key alias in the project's ant.properties file. With this information provided, the build script will prompt you for your keystore and alias password when you perform ant release, it will sign the package and then align it. The final output file in bin/ will instead be <your_project_name>-release.apk. With these steps automated for you, you're able to skip the manual procedures below (steps 3 and 4). To learn how to specify your keystore and alias in the ant.properties file, see Building and Running Apps on the Command Line.
Last edited by coloenz; 22 Mar 2013 at 2:16 AM.
Reason: sencha cms version number added
Just to follow up. This bug is still not fixed, when using Touch 2.2 and sencha 184.108.40.2064
Sencha, I find it strange that you can not reproduce, but I can send you a Cmd-produced apk, signed with Cmd - and then a resigned apk, to see the difference.
I could send you the complete project, but this is easily reproduced with the Cmd standard project, and following the key-creating guide for touch 2.2 in Windows.
I've tested on Win 8 64 bit this time..