With Google Play App Signing, you can securely manage your app signing keys for new or existing apps. Keys are stored on the same secure infrastructure Google uses to store its own keys.
If you lose your keystore or think it may be compromised, Google Play App Signing makes it possible to request a reset to your upload key. If you’re not enrolled in Google Play App Signing and lose your keystore, you’ll need to publish a new app with a new package name.
What exactly is the benefit of using this?
Reading through the link documentation, instead of the Keystore with the App Signing Key I then have an Upload key that has to be handled exactly the same. What’s the difference?
Does anyone have any experience with this with their Ionic apps?
Basically this makes sure that we, the developers, can fuck up and lose our Upload key. It can be replaced. The App Signing key could not be replaced. Now that Google takes care of the App Signing key, this gets easier and the security part is now with a replaceable upload key.
It also enables Google to mess with the uploaded APK (e.g. optimize app size) as “derived APKs” before signing it. Neat! (And actually the most useful change here. I am not sure how much impact this has on Ionic apps though)
Whoah, just created a new app in the Play Console and when you upload the first APK there is now a prompt for automatic app signing as well with a “Continue” button that opts in the app with one click. No way to undo. Shady, Google…
I opted in for App Signing feature the moment I uploaded the very first version of my Ionic App to play store… Sooner I realised one disadvantage for developers, who wants to use “App Update” plugin in their Apps. It Wont Work.
Plugin wont auto update app and if you click update on the prompt you get, it will download the APK from server and end up with “App not installed” message.
So may be if App Update is your priority, you would reconsider joining Google’s App Signing feature.