Keytool Signing Problem: Keystore was tampered with, or password was incorrect

Solution 1:

I don't think you have to include a storepass when you're just doing a list. The storepass encrypts the private key which isn't displayed when doing a list. Just try this:

keytool -list -keystore /Users/salam/Documents/yada/yada

Then provide your keystore password when prompted. If that works then you can try just the keypass on the command line.

You might also want to check and make sure your using the same version of Java. I don't think that's the problem, but if the above doesn't help try it out.

Solution 2:

Somehow on windows, the keytool would not accept the password. I only needed the SHA1 password for configuring the client id on the project on google dev console. The following seemed to work for me

keytool --list --keystore android.jks --protected

This printed the SHA1 keys for all aliases.