Looks like we cannot reproduce this. Please provide another test case to reproduce this issue.
Thank you svenna!
This saved me at least another week of fighting with Sencha.
What I did:
- jarsigner -verbose -sigalg MD5withRSA -digestalg SHA1 -keystore ..\..\..\..\my-release-key.keystore anotherapp.apk alias_name
- # renaming anotherapp.apk to anotherapp.apk_
- zipalign -v 4 anotherapp.apk_ anotherapp.apk
I used CMD184.108.40.2068 under Windows 7.
Wow, I can not describe how happy I am to find this solution. I had been playing with this problem for hours.
Thanks for sharing your solution, shame that Sencha still hasn't solved this silly problem.
I am using the latest Sencha tools, Sencha Cmd v220.127.116.118
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
18 Apr 2013, 10:50 PM
Just to follow up. This bug is still not fixed, when using Touch 2.2 and sencha 18.104.22.1684
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..
19 Apr 2013, 12:28 AM
I am too still having problems, it just does not work as advertised. I sure hope Sencha will do something about this problem now.
Originally Posted by svenna
Have created some bacth files to do the signing for me, but that is far from ideal.
26 Apr 2013, 12:26 PM
still no answer from anybody?
Not going to spend my money over here then. We were planning buying a couple of bundles. But the software just doesn't work. Shame.
Published Android apk gives error “Package file was not signed correctly”
I am using the latest SDK and Sencha Cmd to package for android.
get this error while installing the app from playstore when others try to install the app ?
is it a bug with the SDK or Sencha Cmd
which versions works then. it was working with the earlier versions of sdk and sencha cmd
It's a bug with cmd. You'll have to resign the package manually before uploading to Play Store. I don't think this ever worked, even in earlier versions
Followed the steps of manual resign but still did not work
- Build Release (not Debug) with Cmd 250 - Touch 2.1 GA
- rename .apk to .zip (convenience)
- delete META-INF folder in zip fila
- rename .zip to .apk
- resign with jarsigner: R:\htdocs\dev\bowlingres.no\touchdeploy>jarsigner -verbose -sigalg MD5withRSA -digestalg SHA1 -keystore ..\..\my-release-key.keystore BowlingRes.apk arelease
Followed the steps above but still did not work....
That really did the magic . Thanks alot