Attestation Set Up
Configure attestation to ensure your app has not been tampered with using required information for Android and iOS.
In order to ensure we have everything we need to detect whether your app has not been tampered with as part of our attestation check, we require a couple of pieces of information.
Here is a handy video guide:
Android
For Android, we need your Bundle ID or package name, i.e.com.domain.appname
, which you set in your Unity build settings.
This is NOT the appId ZBD provides you.
We also need the SHA-256 hash of your signing key.
To find your app’s SHA-256 hash key for Google Play:
Access Google Play Console
Sign in to your Google Play Console account.
Select your app
Choose the app for which you need the SHA-256 hash.
Navigate to Release
Go to the Release section in the left-hand menu.
Navigate to Setup
Click on Setup in the submenu.
Select App integrity from the options
Click on App signing
Find the App signing key certificate
Select and copy the SHA-256 Fingerprint
During development, you are likely using a custom keystore in Unity, so we will need that SHA-256 hash as well. You can generate the SHA-256 hash key for your keystore using the following command:
It should look something like this : EA:A1:69:AA:2F:FC:6D:16:84:ED:06:11:E0:65:2B:E0:BB:9C:5B:E3:41:96:06:E2:3D:85:8F:2C:22:2A:E9:86
iOS
For iOS we need your Bundle ID i.e.app id
, e.g.com.domain.appname
and your Team ID.
To find your app’s Team ID for Apple Developer:
Access Appel Developer Account
Sign in to your Apple Developer account
Click on Membershipt details
Select and copy Team ID
This is NOT the appId ZBD provides you.