Signing
View product
v1.0.0
In-App Protection Shielder for Android modifies the application, so the application has to be signed after shielding. The Shielder can sign the application itself, or the application can be signed afterwards with your existing tools.
Signing by the Shielder
The signing inputs are set in a signing configuration file (--signing-config). Example:
keystore_file: ./signing/upload.jks
key_alias: upload
keystore_password: "<keystore-password>"
key_password: "<key-password>"
| Option | Description |
|---|---|
keystore_file |
Required. Path to the keystore. Relative paths are resolved from the signing configuration file. |
key_alias |
Required. Alias of the signing key. |
keystore_password |
Required. Password of the keystore. |
key_password |
Required. Password of the signing key. |
The signing configuration file contains passwords. Do not commit it to version control.
Signing After Shielding
The shielded application can be signed with the standard Android tools. When the application is published with Play App Signing, sign it with your upload key.
APK
Align the APK with zipalign (build-tools 35 or later) and sign it with apksigner:
zipalign -P 16 -f 4 App-shielded.apk App-aligned.apk
apksigner sign --ks release.jks --ks-key-alias release --out App-signed.apk App-aligned.apk
AAB
Sign the AAB with jarsigner:
jarsigner -keystore upload.jks -signedjar App-signed.aab App-shielded.aab upload
Read Next
Last updated on Oct 29, 2026 (16:36)
View product