Bleurgh! error package file was not signed correct
Monkey Targets Forums/Android/Bleurgh! error package file was not signed correct
| ||
| Recdently updated one of our apps, signed as normal and uploaded to Google Play without problems. Now I'm getting users complaining they can't install, and that they get the error "error package file was not signed correctly" Any pointers? I'm using the new experimental Android build, latest version of Java (8) etc. Some googling hints Java is broken post version 6, so I guess I could try going back to all that stuff. Anyone else seeing this? App in question is this https://play.google.com/store/apps/details?id=com.yzr2 Stoopid that Google Play lets you upload and publish when the crypto's borked in some way. Grrr. |
| ||
| may have solved, will post update later if that's the case. |
| ||
| I just tried installing it and got this error ( |
| ||
| I tried again and now everything is fine! Cool game btw |
| ||
| I hope the error was caused by Google Play serving up the old version, then when you retried you got the updated version. Thanks for the positive feedback on the game as well :-) In terms of the solution, I think the problem relates to signing the apk with jarsigner when you are using JDK 7 or above. It needs some extra parameters supplying (which I hadn't done since I was used to signing with JDK 6). The parameters are the -sigalg and -digestalg ones, so I basically had to add -sigalg SHA1withRSA -digestalg SHA1 into the command for signing the apk See http://qt-project.org/forums/viewthread/35056 which refers to http://developer.android.com/tools/publishing/app-signing.html#signapp for more info.. |
   |