Menu
Android requires that all apps be digitally signed with a certificate before they can be installed. Android uses this certificate to identify the author of an app, and the certificate does not need to be signed by a certificate authority. Android apps often use self-signed certificates.
Signing is encrypting with the private key. Because you publish the public key the app store and the users have your public key. They can decrypt your app and therefore know for sure that the app is really your own.
Android requires that all APKs be digitally signed with a certificate before they are installed on a device or updated. When releasing using Android App Bundles, you need to sign your app bundle with an upload key before uploading it to the Play Console, and Play App Signing takes care of the rest.
When I login to my Google Play developer Console, I see this:
I understand how Google Play App Signing works, in general it keeps the app signing key on behalf of you, and I need to use another so called "upload" key to sign my app and submit to Google Play Console for app signing.
But, my question is:
I already published my app without using Google Play App Signing half year ago, now, if I opt-in to Google Play App Signing, would it affect my already released app? Or Does it go smoothly with my published app if I switch to Google Play App Signing?
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With