A month ago I deleted the .jks file thinking it was a duplicate.
I had a file of the same name in my backups, unfortunately I deleted the wrong file and the file I have is not identical to the base signature
I lost the jks keystore file for publishing my app on google play console.
The best solution is to contact the support service. from Google.
You are requesting a reinitialization of the signing key. He will contact you directly by gmail.
I tested and they helped me quickly
Related
Using the Sketchware app and Android, I am trying to export to the Google Play store, I have to select the .json for the service account to allow it to publish the app.
However, when I try to select the .json file I have downloaded to my phone, I navigate to the directory the .json file is stored in then when I try to click on it, it is greyed out and I cannot click on it.
(P.S.: I have tried contacting Sketchware support. However, it has been over three days now and I understand due to coronavirus the response may be delayed, but I thought I would ask here if anyone has a solution.)
Why are you publishing the app directly from Sketchware to PlayStore?
You better sign the apk usin APK SIGNER app and manually upload the APK to the Play Console.
I have never used Google Play Console before, but I think this could help you:
Download your app
Using Apk Extractor (play.google.com/store/apps/details?id=com.ext.ui) is a software that will help you to get APK file from an pre installed app from Android ONLY. Using this software you can actually get an APK or Android Package that you can use while publishing app
There are many application available on Google Play that can convert your app file to AAB format.
Yes, download Apk editor and select generic key or test key (try them out, there's a few) in settings in the app, and edit the API version to the correct number. And set up a Google Play console account.
Yes, we do have a solution. Send the file to WhatsApp. Then share it from WhatsApp, choose file manager, copy the file to the place that you want, open sketchware, choose the file that you added in the JSON file, and enjoy.
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.
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.
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.
This is NOT a request to extract the private key from a .apk file.
I am having a problem signing a new .apk file with same key as the old .apk. This is important to do because it is required by Google in order to update the app in Google Play.
I am "sure" that I have the keystore file and passwords, but I am still having a problem.
One of the debugging steps I would like to perform is extracting any information about the key from the old .apk file. I know I cannot get the private key itself (for obvious reasons). I just want to see the name or other information so I can do a sanity check on getting the keys to match.
My questions are:
1) What information can be extracted from a .apk file regarding key and keystore used to sign it?
2) How do I extract that information?
My preferred platform is Mac, but I can use Linux or Windows as well.