I created a test application on the Play Store to test the Google Play signature features. As soon as I create a test application and enable this feature, I got access to the “Deployment Certificate”. I did not download it and did not use it. Following are the following steps:
- Then, using Android Studio, I create a new keystore, password, and create an alias with a password (as usual).
- I signed the application with the keystore created in step 1. We downloaded the application to the Google Play Store.
- Upload key certificate uploaded. Added a download key certificate to my keystore created in step 1 using the command
keytool.exe -importcert -file upload.der -keystore mykeystore.keystore - Verify that it has been added to the keystore using the
keytool.exe -list -keystore mykeystore.keystore . Now there are two aliases, a new alias (named mykey), added in step 3. It refers to a trusted type certificate.
Now, since “trusted certificate entries are not password protected,” Android Studio does not allow me to sign an application without a nickname password, and of course, I cannot use a random password because it is “not password protected”. How to use it to sign my apk for future updates? Am I missing something important here, or is my understanding wrong?
android google-play
Atif farrukh
source share