Key alias missing in eclipse when signing android APK

I have already created a keystore, signed apk and published it also in the Play store.

Now I made some bug fixes using the same keystore and password, and clicked further in the application wizard to export.

He shows me a field for an alias, without an alias on it. But the same material worked for me yesterday to sign the same project, and now it looks empty.

I also tried it on the command line, but it says: "Vault repository or invalid password", but I am sure that the password identifier is correct, as well as the key repository.

This is a show stopper for me. Please, help!

+6
source share
6 answers

You must first verify that you have entered the correct password. If you enter the wrong keystore password when you perform a signed export to Eclipse, the drop-down list of aliases in Eclipse will be empty (and not editable). Also in the dialog box the message “Keystore has been changed or the password is incorrect” will be displayed at the top instead of the message “Enter key password”.

If you are absolutely sure that you have the correct password and are using the correct keystore, then the only other explanation I can think of is that something went wrong with the keystore. Perhaps you saved it as ASCII in CVS / SVN?

+7
source

I had the same problem and after a long search I was able to fix it.

WHAT IS THE CAUSE OF AN ERROR?

This error occurs when

  • You typed an invalid keystore password
  • For some reason, your keystore is corrupt

MY CASE Script

In my case, I used the correct password, which means that my keystore was damaged.

Everything worked fine since I renamed my application and I changed the location of the keystore and apk. Then I was confused about where the keystore and apk are located, in this confusion I could replace the keystore with a new apk , which damaged the keystore, but I can not be 100% sure.

HOW I SAID IT

The fix was simple. For win7: Find the "original" keystore that was damaged, right-click it, select "Properties", "Previous Versions", select an earlier version when the keystore was in order, and click "Restore"

When you click "Previous Versions", you have to give it time (mine took 30 seconds). If nothing happens, then the key store that you are trying to restore may not be "original", it may be a copy or something else.

(I say "original" because I tried other ways to fix this error, and I had to make copies of the keystore, therefore, to use the original damaged keystore )

IF NEVER CONTINUES

If you did this and still Eclipse is not showing an alias, you may have changed the key store directory, just like me.

If you changed the keystore directory, you should do the above and then put it in the previous directory where it worked, otherwise eclipse will not find the alias!

To find out if your keystore works without using Eclipse, you can use KeyTool.

  • Find the Java JRE bin folder where keytool.exe should be (mine was C: \ Program Files \ Java \ jre1.8.0_25 \ bin)
  • Create a copy of your keystore (to simplify)
  • Open a command prompt and run these commands

cd C: \ Program Files \ Java \ jre1.8.0_25 \ bin

keytool -list -keystore "yourkeystorename"

Then you should ask for the keystore password if the keystore is not damaged yet, which means that the restore did not work.

Remember to make copies of the working keystores every time you publish the application, and you know that the keystore works fine.

+2
source

I think you entered the wrong password ... please make sure the password is currect ... otherwise the alias name does not appear in the drop-down list.

or

Maybe your keystore location has been changed ...

+1
source

if you remember the name, try to introduce it as new, it will force to update.

0
source

Experienced the same problem: in my case, I mistakenly entered the password for the first time, so it did not fill out the list of aliases.

If you remember the password, simply “Clear all projects” → “Build” and continue the first time. It worked and successfully uploaded to Google.

0
source

Sorry, but I had the same problem, and I realized that all I was missing was where I put the key when I saved it in another folder. When I tried to update the APK, it did not show the key alias, because there was no key in the folder I was trying to read it. So I realized that I saved it in another folder. As soon as I moved the correct folder, a key alias appeared and everything was in order.

0
source

Source: https://habr.com/ru/post/925921/


All Articles