Problem starting my signed keystore in Eclipse

Question

I cannot start my signed keystore in Eclipse:

I get an error message:

Keystore was tampered with, or password was incorrect 

How can i solve this?

Here is the error:

So I successfully signed the keystore:

Answer 1

In Windows-> Preferences-> Android-> Build, you can just change your DEBUG KEYSTORE. The Keystore specified there is not intended to sign an application for release, but only for debugging.

Like the default debug key store, the user debug store should have the following:

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

With the exception of the name of the keystore itself, information about organizational units, and the key part of the alias, all data must be the same as the default for the debug storage

Answer 2

I can advise that I want to advise you to check the password for the corresponding language and case, and also make sure that your keystore is in a consistent state (but has no idea how to do this if you have not created a checksum).

General recommendation for keystores: always back up.

In addition, the keystore is to make sure that you are the one who created the application at the time of its update. IOW is a tool that only allows you to update your application.

Answer 3

Shihan, I support Vladimir’s offer to reserve your keystores.

To avoid getting caching errors Just back up the current keystore and then delete it (from / home / user / .android / debug.keystore) and recompile the application and eclipse will automatically create a keystore for you.

Always back up your keystores to publish / republish the application.

Good luck

Answer 4

The easiest way is to create a keystore from the innermost eclipse as part of the export process. When you export your application, click on it to create a new keystore. Fill out the relevant information and Eclipse will create a new, valid keystore for you.

And always back up your keystores. I have a USB drive that has a copy of all my key stores.

Answer 5

I am confused by what you are trying to achieve here. Is it that you simply cannot edit it as it is? In preparation for delivery to the market, you will export it without a sign (i.e. without debug storage).

Maybe you have the option "forced error when using external cans ..."?

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

Assuming you have already done this, I won’t be “Google for you,” but it could be an eclipse problem.

I hope you do it soon.