In order to make an APK application available through Amino management platforms it is necessary to first configure the system with the APK fingerprint. This is a simply process which must only be performed once for each application. The process does not need to be repeated when deploying new versions of the app if the fingerprint has not been changed.
Authorizing a new Application APK
Before uploading a new Application APK the fingerprint must be installed. If you upload an application before following these steps you will receive the following error message:
Engage and Orchestrate require the SHA-1 fingerprint string from the apk file to be entered in to the system by an Amino Support Agent before the APK itself can be uploaded. This is a security measure to prevent unauthorized apps from being uploaded. The SHA-1 string is rendered as a hexadecimal number, 40 digits long that is typically found in the ./META-INF/ directory of the apk file. It will be in a .RSA file depending on your apk, typically named CERT.RSA or BNDLTOOL.RSA but your app may differ.
1. Ask your Android app provider to provide you the 40 digit SHA-1 string then continue to step 4 below.
2a. You can find it yourself in a Linux environment using keytool:
sudo unzip foo.apk
sudo keytool -printcert -jarfile foo.apk OR keytool -printcert -file /META-INF/CERT.RSA >> fingerprint.txt
Look for the line similar to this example in your output file:
2b. If your application does not have an .RSA file then it may be signed in v3 in which case you can use the apksigner tool.
sudo apt-get install apksigner
./apksigner verify --print-certs foo.apk
3. Copy and paste the SHA-1 line without semicolons in to a .csv file
4. Raise a support request with the Amino customer support team and attach the .csv file to the ticket. The support team will upload the application fingerprint and notify you when this has been completed
When you have received this notification you will be able to upload your application APK to Orchestrate or Engage.