Generating a signed APK

Requirements

Clover apps require that you sign the Android application package (APK) using only the v1 (JAR-based) signing scheme. If your build tools support v2, v3, or v4 signing scheme, ensure that those versions are disabled.

๐Ÿ“˜

Note

For more information about this restriction, refer to: https://docs.clover.com/docs/android-10-romnotes-for-clover-developers#apk-signature.

Generating a signed APK

To generate a signed APK for the Clover App Market, use an Android-approved tool, such as apksigner or Gradle.

๐Ÿ“˜

Note

The following links are some examples of respective third-party vendor documentation. These links are subject to change without notice.

Clover example with apksigner

This is an example for using the apksigner to enable v1 signing scheme, and disable v2 and v3 signing schemes. This example is for illustration purpose only. Please verify any steps with the vendor documentation.

`$ apksigner sign --ks test-release.jks --v1-signing-enabled=true --v2-signing-enabled=false --v3-signing-enabled=false app/build/outputs/apk/release/app-release-unsigned.apk`

๐Ÿ“˜

Note

The preceding example was generated using Android Build Tools version 30.0.3. When new versions of Android Build tools are released that support additional signatures, they will need to be excluded.


Did this page help you?