Hello, I know this is an Android Publishing issue, but I find insteresting to talk here about it because it's an evil trap ! 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 (32bits), 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). And it comes with "SHA1withDSA". (You can check your keys in a keystore with the command: [JDK_PATH]\keytool -v -list -keystore "[YOUR_PATH]\[YOUR_NAME].keystore" 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 ! Right now, I do not know what to do, I'm waiting answers from google^^. If anyone knows how to CHANGE an algorithm from a .keystore WITHOUT deleteing/creating a key, you're welcome!