Ok folks.. long story short, I was developing on a computer that I no longer have access to. I was able to retrieve the source code, but not the .keystore file used to sign
It is possible for a long while.
keytool -genkeypair -alias newalias -keyalg RSA -keysize 2048 -validity 9125 -keystore nameofkeystore.jks
This key must be a 2048 bit RSA key and have 25-year validity.
keytool -export -rfc -alias newalias -file upload_certificate.pem -keystore nameofkeystore.jks
Then upload this pem file and fill the form and submit it to this site . And then you will receive an email once we've registered the new upload key . Only accepts key reset requests from the Play Console account owner.
All well and good. You can publish new release apk with your new jks file.
If you know your keystore password, you still don't have the associated private key to sign your app. You also have no chance to generate the same private key which corresponds to your public key.
Therefore: Always backup your keystore file. It's as important as your source code.
I have generated the signed apk using android studio , so in the "key Store Path" i just typed some name without extension, and fill this popup and signed the application.
next time for publishing the application i don't remember the path and name where it was created.
somehow i find the default location which is "C:\Program Files\Java\jdk1.8.0_45\jre\bin" : \jre\bin
and in that folder short by date ,then i tried with recent file and it worked for me.
Note : you should remember the Key store password and key password.
Faced the same problem. I was trying to restore it via deleted files restoring tools, but it failed. So, there is no other way: you should issue another application.
Generally, the only advise that exists on keystores: "always back it up!"
From long days, I also search a solution for that, but not successfully till now. If you have the last version of your app apk, then you can retrieve certificates from that by using the jarsigner cmd command. But you need a private key for update. Google Play did not provide any relaxation for that.