Some Android developers may elect to sign their apps using Google Play (instead of signing the Fused app on Appdome) and allow Google to manage the signing certificate. In order to do this, you need to extract a SHA-1 or SHA-256 Fingerprint from the Google Play signing certificate.
This Knowledge Base article provides instructions on how to extract the SHA-1 or SHA-256 fingerprint from a Google Play signing certificate when the developer has selected Google to manage the certificates.
Extracting SHA-1 or SHA-256 Fingerprint from Google Play App Signing Certificate
Appdome is a mobile integration platform as a service (iPaaS) that allows users to add a wide variety of features, SDKs and APIs to Android and iOS apps. Using a simple ‘click to add’ user interface, Appdome allows anyone to easily integrate features to any mobile app – instantly, no code or coding required.
To use Appdome’s private signing, you need the SHA-1 or SHA-256 fingerprint from the signing certificate from your Google Play account.
If you enable Google app signing when uploading your Fused app to Google Play, you need to enable “Private Signing” on Appdome before uploading the fused app to Google Play. The Private Signing option is located under the “Sign” tab after you fuse an Android app. If you don’t enable Private Signing, when you sign the app on Google Play will trigger Appdome Anti-Tampering.
How to Extract a SHA-1 or SHA-256 Fingerprint from the Google Play App Signing Certificate
- Navigate to the Google Play Console and login
- Choose the application you are signing
- Go to Release Management –> App Signing
- Copy /Download the SHA-1o r SHA-256 certificate fingerprint from the App signing certificate section
This app signing certificate SHA-1 or SHA-256 is the fingerprint of the final singing certificate that will be distributed via Google Play. Insert this value while signing on Appdome. The reason Appdome requires this value is that several Anti-Tampering techniques within Appdome ONEShield rely on the final signing certificate fingerprint in order to protect the application and verify it has not been re-signed by an attacker or otherwise tampered with.
For more information on Google App signing, visit this resource.
To zoom out on this topic, visit Appdome for Mobile App Security on our website.