Generating Signed APK with no key store password

I got a half completed project 7 months ago that was made with Android Studio and they had also generated a singed APK and put it on the Google Play Store.

Android Studio

APK

Now that I have finally finished the project I would like to place it on the Google Play Store or update the project that they had put in the Play Store.

Play Store

They gave me their Google Play Store username and password so I can access the app but they forgot to save the key store password they signed the APK with.

key store password

Now I have found myself in a position where I cannot generate a signed APK to put it the Play Store nor can I update the existing app.

If possible I would like to update the existing version but if not then putting a new app on the store will suffice.

What can or what should I do in this situation?

1 Answer
1

Unfortunately, since Android requires that all APKs are digitally signed with a certificate, you can't publish a new version of the app without the keystore.

As stated on the docs:

Loss of the app signing key means that an app cannot be updated, so it is critical for it not to be lost.

You'll have to create a new Keystore and republish the app. Also, don't forget to backup this new one, and to store the password somewhere safe.

Take a look at the docs. There are currently two ways of signing and publishing your apps throught the keystores.

The first way is to create and handle the keystore yourself, like it was done in the past.

The second way is to use Google Play App Signing.

When using Google Play App Signing, you will use two keys: the app
signing key and the upload key. Google manages and protects the app
signing key for you, and you keep the upload key and use it to sign
your apps for upload to the Google Play Store.

The main advantage of this method is:

When you use Google Play App Signing, if you lose your upload key, or
if it is compromised, you can contact Google to revoke your old upload
key and generate a new one. Because your app signing key is secured by
Google, you can continue to upload new versions of your app as updates
to the original app, even if you change upload keys.

Since you're going to have to republish the app, consider using the second option instead.

Key store path

Required, but never shown

Required, but never shown

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.