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.
Related
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/
After my hard disk crash, I've lost all my data including the keystore file. Though I remember all the information I have inserted to generate the keystore file. Now without the keystore, I can't update my app in google play store :(
Google play is showing me this error now:
...
Is there any way to generate the JKS file so that it lets me upload the APK in the Google play?
After my hard disk crash, I've lost all my data including the keystore file
Restore it from the backup that you made of your hard drive. If you are not backing up your computers, stop using those computers until you start backing them up.
Is there any way to generate the JKS file so that it lets me upload the APK in the Google play?
No.
Well there was an accident on my computer with it I lost my project and my key to my application. How can I decompile the application and sign with new key?
Long story short, you can retrieve source with some external tools like javadecompilers.com (explained there)
However for your key, you will have to create a new application in the store unfortunately, using a new key (explained here). There's no way around if you don't have it elsewhere.
if you have the .apk, it is actually just a zipped file. For example with 7zip you can right click on the apk file and "extract files".
You will then need to have a new key and sign it.
Only problem i see is if the app was already released, you have to use same account, or else maybe the store will assume you publish someone else code (not sure about that)
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 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....