CODEWITHSUNDEEP
androidandroid-studiogoogle-playgoogle-console-developer
Nanda Z
Nanda Z

Reputation: 1876

Create new keystore for new application release

I want to release a new application. And I have created a keystore specifically for that application. When on the Google console I accidentally clicked on enabling Google Play App Signing. My APK upload failed because it did not match the application signer. I have long lost the application keystore before. How can I release a new application with a new keystore? Explanation from Google makes me even more confused, can I give me the order that I have to do.

My error on console looks like this:

enter image description here

And the upload certificate section is written like this:

Your application does not have an upload certificate. The certificate you use to sign the first APK will be used as an upload certificate.

Upvotes: 1

Views: 446

Answers (2)

Nanda Z
Nanda Z

Reputation: 1876

I want confirmation that I have found the answer, via this link [Android Signed APK showing as Unsigned APK when trying to upload to production I have to check both options when generating a signed APK.

There are three choices available to us:

select V1 (For older version of signing) - apk gets uploaded successfully

select V2 (For newer version of signing) - Please note that selecting this alone will not work.

select V1 and V2 (For older and newer version) - apk gets uploaded successfully

Why selecting V2 alone does not work ?

Because APK Signature Scheme v2 was introduced in Android 7.0 (Nougat). To make a APK installable on Android 6.0 (Marshmallow) and older devices, the APK should be signed using JAR signing before being signed with the v2 scheme.

thank you for participating in helping find answers

Upvotes: 0

Aashutosh Poudel
Aashutosh Poudel

Reputation: 110

While generating signed APK, Just check on Both signatures version i.e

Upvotes: 1

Related Questions