I am trying to make a signed apk in android studio on a machine that I did not originally create the keystore file on, and I am getting the error from the title. I know for a fact that I am getting the password correct because I have 2 copies of the password written down and I have successfully created a signed apk multiple times on the machine the keystore was originally created on. I am wondering if I am getting this error that the file was tampered with or the password is incorrect because I cannot transfer the keystore files between computers? I certainly hope not because I will not have access to the original PC until the end of August. Any information is greatly appreciated
I have used key store many times on different machines.
It works perfectly without any problem.
As you told you noted down the password. Problem must be there with the key alias or you must be using some other jks file to generate the apk.
Lastly this might help
https://www.linkedin.com/pulse/forgot-keystore-passwordjks-file-you-can-still-recover-saswat-sahoo/
Related
I'm trying to upload a game to Google, I've already uploaded version one, so I have to jump through frustrating hoops to get version 2 signed. It won't allow me to create a key Store alias or whatever, all the information I've put into the game is Company (com.DefaultCompany.Blaster) and Skies Above as name, but before when I filled the information out I was getting certification errors so I've restarted the project. This is the most frustrating thing I've ever had to do and have spent well over 5 hours trying to figure it out. Could someone run me through trying to get a signed APK with the right certification so I can upload my game? Thanks.
I believe it's because you setted the Key Store path as an apk file instead of a jks file (as shown below from Android docs) which should be kept in a safe directory at all times since the keystore is what provides access to the apk release process after all. That said, you may need to release a new apk with the new keystore jks file, and yes, that means publishing a new listing for your app at the Play Console.
I am picking up an Android application after a year away from the codebase. I attempted to export a signed application package but cannot for the life of me remember where the original keystore was. I also don't know the name of the keystore file (and it appears that keystores don't have a file extension either).
What are my options for retrieving the keystore so I can submit an update to the Play store?
Don't waste your time.
There no way to submit an update without having the same keystore files,
unless you find the keystore that was used to the submitted app.
Keystore files does not have an extension. What I do is to a .keystore extension when saving them.
e.g. someName.keystore
This way I can search them and find them easier.
I found alot of topics with the same problem but they always lost their password. I have the password still in my KeyPass but I have lost my keystorefile. Is it possible to restore it with help of the password or anything else? Google Play doesn't let me update my app :/
Unfortunately, there is nothing you can do to update the app once you lose the keystore file. Your next best option is to just release the update as a new app and inform as many of your users as you can.
not possible. if keystore file lost nothing can be done
No you must need that same key store to update your app. Other wise you need to create new keystore and upload it as new app by changing projects package name in manifest file.
I thought I lost my keystore file too. Turns out, using Windows operating system, the keystore files were put into a virtualized folder for security purposes. All my keystore files were in there. That folder is off limits to explorer for some reason so searching for .keystore turned up nothing. The only way I found it was to point explorer to the directory used when executing the original keytool generate command. When you do that, there is a button on the top of the explorer window which says 'compatibility files'. Click that and the keystore files appear. Hope this helps someone.
I think my KeyStore is somewhere on my Mac, but I can't seem to find where. I have already signed a previous APK with that KeyStore, but have since inconceivably lost it. I have used programs like Find Any File to no avail. Is there any way to get any kind of information about the keystore from the APK? e.g. Name, Date Created, etc....
I have already created a keystore, signed the apk and published it the Play store as well.
Now I have made some bug fixes, using the same keystore and the password and clicked next in the export android application wizard.
It shows me a drop box for alias name, with no alias name on it. But the same stuff has worked for me yesterday to sign the same project and now it appears empty.
I also tried it on the command line but it says "keystore tampered or password incorrect", but I am very sure the password id is correct and so is the keystore.
This is a show stopper for me. Please help!
First you should check if you really typed the correct password.
If you type the wrong keystore password when doing a signed export in Eclipse then the alias dropdown list in Eclipse will be empty (and non-editable). Also the dialog will show the message "Keystore was tampered with, or password as incorrect" on 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 has gone wrong with the keystore. Perhaps you saved it as ASCII in your CVS/SVN?
I had the same problem and after a long time of searching I managed to fix it.
WHAT CAUSES THE ERROR?
That error occurs when
You have typed wrong the keystore password
Your keystore has been damaged for some reason
MY CASE SCENARIO
In my case I used a 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 got confused about where the keystore and the apk is, in that confusion I might have replaced the keystore with the new apk which damaged the keystore but I cant be 100% sure.
HOW DID I FIXED IT
The fix was simple. For win7: Locate the "original" keystore that was damaged, right click on it, choose Properties, Previous Versions, choose an earlier version when the keystore was ok and click Restore
When you click on Previous Versions you have to give it some time (mine took like 30sec). If still nothing happens then the keystore you are trying to restore might not be the "original", it might be a copy or something.
(I say "original" because I tried other ways to fix this error and I had to make copies of the keystore, so to be sure use the original damaged keystore)
IF STILL NOTHING HAPPENS
If you did the above and still Eclipse does not show the alias you might have changed the directory of the keystore as I did.
If you have changed your keystore directory you should do all the above and then place it at the previous directory where it worked, otherwise eclipse will not locate the alias !
To see if your keystore works without using Eclipse you can use the KeyTool.
Locate you Java JRE bin folder where keytool.exe should be (mine was C:\Program Files\Java\jre1.8.0_25\bin)
Make a copy of your keystore there (to simplify things)
Open a command line and run those commands
cd C:\Program Files\Java\jre1.8.0_25\bin
keytool -list -keystore "yourkeystorename"
Then you should be asked for the keystore password, if not the keystore is still damaged which means that restore did not work.
Remember to make copies of the working keystores every time you publish an application and you know the keystore works fine.
i think you entered a wrong password...please make sure that password is currect...otherwise the alias name is not shown in dropdown list..
or
May be your keystore location is changed...
if you remember the name, try to introduce it as a new one, it will force the refresh.
Experienced the same issue, My case I wrongly entered the password for first time, so it didnt populate the alias list.
If you remember the password, just Clean All projects -> Built and continue from first. It worked and successfully uploaded to Google play.
Sorry but I had the same issue, and realised that all I was missing was where I put the key as I stored it in another folder. When I tried to update the APK it didnt show the key alias cause there was no key in the folder I was trying to read it from. So I realised I had saved it in another folder. Once I relocated the correct folder the Key Alias showed up and was all good from there.