I made exactly the same mistake ! Customers that buy my newly released game have an "Package file was not signed correctly" error. I find that I signed my key with JAVA 1.7 keytool, that used as algorithm "SHA256withRSA" I was thinking this - default - algorithm is not supported by Android Publishing, and provoke this error.
So I rolled-back to JAVA 1.6, delete my key from my current keystore, and re-create one (same name) with "SHA1withDSA" I thought that will solve my signature problem, but when uploading it in Google Play I encounter the message: "The apk must be signed with the same certificates as the previous version." I'm really disapointed, the purpose of the new update was specifically to change my current certificate ! What can I do to release my application ? PS: maybe someone know a command to change the algorithm with keytool without deleting/creating perhaps ? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
