Solution Lost App Keystore update issue SHA1 MD5 certificate fingerprint error Generate pem file

Tech Solution 0 Comments

Solution Lost App Keystore update issue SHA1 MD5 certificate fingerprint error Generate pem file Check android studio jks APK upload Certificate error android studio Keystore jks upload an APK that is not signed with the upload certificate

Show this type error if Keystore SHA1 MD5 certificate fingerprint not match

your upload an APK that is not signed with the upload certificate. you must use the same cerificate.
the upload cerificate has fingerprint

ShA1;05:dd:ss:rr:03:03:09:wwe:cc:c3:ce:d4:tt

and the certifiate used to sign APK your Uploaded have fingerprint

ShA1;05:dd:ss:rr:03:09:wwe:cc:c3:ce:d4:tt:rr:t4

Q 1) How to solve Lost Keystore or not match for App update keystore issue solved SHA1 MD5 fingerprint certificate APK upload Certificate error android studio Keystore jks

Contact with  google play developer support team and solve App update keystore issue

1) Login google play developer console
2) Go to App Signing
3) check Upload certificate (MD5 certificate fingerprint) (SHA-1 certificate fingerprint ) same your upload keystore file
How to check SHA-1, MD5 same or not check detail in end of this page (Q 3)

4) If Not Match GO to ( contact the developer support team ) show option in bottom of the page
5) Fill form (General Play Console issues)
First name, Email address, Developer name (Click on ? option and click on Link show in popup file),
Developer Account ID (Click on ? option and click on Link show in popup file),
Application package name (Click on ? option and click on Link show in popup file),
Click I have a key or keystore related issue

Give feedback or describe your issue: copy past error show

Upload screenshot error show

6) last submit

you get reply with in 2 days for google play developer suppor (googleplay-developer-support@google.com)

May be google asked upload pem file

google play developer suppor automatic reset keystore file

And at last You can upload apk file with same keystore file for no more changes

Q 2) How To Generate pem file and send google play developer support keystore file path check

How To Generate pem file and reply to googleplay-developer-support@google.com keystore file path check

1) download and install keystore-explorer software. download and install keystore-explorer software according to operating system Windows, Mac, Linux,

Link: http://keystore-explorer.org/downloads.html

2) Go to File and open Keystore file
3) Enetr password same for Keystore or android
4) click on Keystore file
5) Go to last option PEM Click
6) Click on Export
7) Set Location path save file
8) write file name with .prm Eg project.pem

So save the PEM file and send to google

how to check keystore file path android studio check Q 4

Q 3) How to check keystore fingerprints SHA1 MD5 code, keystore file path check:

How to check android studio keystore file SHA1 MD5 code is same with your google play developer console account

MD5: 00:0000:8888:3:7F:AE
SHA1: 49:00000: E6:17:69:7D:C9

1) download and install keystore-explorer software. download and install keystore-explorer software according to operating system Windows, Mac, Linux

Link: http://keystore-explorer.org/downloads.html

2) Go to File and open Keystore file
3) Enetr password same for Keystore file or android
4) click on upload Keystore file name
5) last show fingerprints in last option keystore fingerprints SHA1

Now check keystore file SHA1 MD5 code is same with your google play developer console account

Q 4 how to check keystore file path android studio jks format certificate keystore

1) Open android studio
2) Go to Build
3) Go to generate signed bundle or apk
4) Go to APK file or bundle
5) Check Key Store Path folder in .jks (jks format certificate) .jks format keystore

C:\Users\username\.android\applicationnamefoler\nameprokect.jks

 

If Lost App Keystore file and show update time issue SHA1 MD5 certificate fingerprint error and you can contact with google play developer support team via fill the form Login google play developer console check Q 1 and than start your message conversation with google play developer support team like this

 

First email you can racived Google Play Developer Support team.

Thanks for contacting the Google Play Developer Support team.

The ticket number for your support request is referenced in the subject line of this message, and you should receive a response from us within 2 business days.

We ask that you do not send duplicate tickets as this will not reduce response time.

We appreciate your patience while we process your request.

Regards,
Google Play Developer Support Team

——————————————————————————

2nd email you can racived Google Play Developer Support team.

Meining that create PEM file and reply

Hi there,

Thanks for contacting Google Play Developer Support.

Now that we’ve verified your account, I’m happy to help you reset the upload key for your app, app name. The new upload key will be used to sign APKs that you upload to Play.

We recommend that you adjust your planning to include a buffer period of 48 hours from when the upload key has been reset before you can use the new upload key. You can learn more about using app signing by Google Play here.

Here’s how to generate and register a new upload key:

Follow the instructions in the Android Studio Help Center to generate a new key. It must be different from any previous keys. Alternatively, you can use the following command line to generate a new key:
keytool -genkeypair -alias upload -keyalg RSA -keysize 2048 -validity 9125 -keystore keystore.jks

This key must be a 2048 bit RSA key and have 25-year validity.
Export the certificate for that key to PEM format:
keytool -export -rfc -alias upload -file upload_certificate.pem -keystore keystore.jks

Reply to this email and attach the upload_certificate.pem file.
I look forward to your response. Please let me know if you have any questions in the meantime.

Regards,
Emily
Google Play Developer Support

Did you know we offer chat support in English? You can chat with us Monday through Friday, 12 a.m. to 12 a.m. Greenwich Time (GMT).

 

————————————————————————–

Upload PEM file and

————————————————————————-

3rd email

Hello,
We received a request to reset your upload key for app name. The new upload key will become valid on Apr 17, 2020 at 5:40 AM GMT. Until the new upload key becomes valid, you can’t upload any new APKs.

New upload certificate fingerprints:
MD5: 00:00:00:000:10:9D:1B:CD:F3:0d:90
SHA1: 49:00:ee:FF:F0:71:pp:E6:17:kk:7D:C9

If you didn’t request a reset, let us know.

Sincerely,
The Google Play team

————————————————————————————

Good news – I was able to register a new upload key for your app. The new key will be usable from: 2020-04-17 05:40:23 UTC time, this is not your local time.

Make sure to update your keystores in the following locations:

Local machine
Locked on-site server (varying ACLs)
Cloud machine (varying ACLs)
Dedicated secrets management services
(git) repos
Thanks for your patience during this process, and please let me know if you have any other questions.

I wish you healthy days. Take care!

 

Now you can upload new APK file and automatic file upload and no any error show if you are follow this process

 

What is solution APK not signed error Solution Lost App Keystore update issue SHA1 MD5 certificate fingerprint Generate pem file Check android studio jks keystore file path check upload