Problem running my signed, release keystore in Eclipse

Question

I am unable to run my signed, release keystore in Eclipse:

I get the error:

Keystore was tampered with, or password was incorrect

H

Answer 1

The obly thing i can advise is to check the password for the appropriate language and case, and also make sure your keystore is in consistent state(but don't have a clue how to do it, if you haven't generated checksum).

The general advise for keystores: always make a backup.

Also, keystore is the thing to make sure you're one who have created the application in the moment of updating it. IOW, it is a tool to let only you update your application.

Answer 2

Sheehan , I support Vladimir's suggestion to backup your keystores.

To avoid getting keystore errors Simply backup the current keystore & then delete it(from /home/user/.android/debug.keystore) & recompile the app & eclipse will automatically generate a keystore for you.

Always do backup your keystores for publishing/republishing the app.

Good Luck!

Answer 3

In Windows->Preferences->Android->Build you can just change your DEBUG KEYSTORE. The Keystore you specify there, is not for signing an app for release, but just for debugging.

Like the default debug keystore, the custom debug keystore needs to have the following:

Keystore password: "android"
Key alias: "androiddebugkey"
Key password: "android"

Except for the name of the keystore itself, information about the organizational units and the key behind the alias, all data have to be same as the default debug keystore

Answer 4

The easiest way is to create a keystore is from inside eclipse itself as part of the export process. When excporting your app click the option to generate a new keystore. Fill out the appropriate information and Eclipse will generate a new, valid keystore for you.

And always backup your keystores. I have a usb drive that has a copy of all of my keystores.

Answer 5

I am confused about what you are trying to achieve here. Is it that you just can't edit it as it is? When preparing it for delivery to the market, you would be exporting it unsigned (ie without the debug keystore).

Could it possibly be that you have the "force error when external jars..." option checked?

I third (or fourth) what others have said here about backing up and deleting the keystore at ~/.android - http://developer.android.com/guide/appendix/faq/troubleshooting.html#signingcalendar.

Assuming that you've already done so, I won't "google that for you", but it might be an eclipse problem.

Hope you get it going soon.