Generate 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.
Generate a signed APK
To generate a signed APK for the Clover App Market, use an Android-approved tool, such as apksigner
with the --v1-signer-name
parameter or Gradle. The --v1-signer-name
parameter saves the signature file with a name you designate. Without a designated name, the signature file name defaults to use the key name.
Note
The following links are some examples of respective third-party vendor documentation. These links are subject to change without notice.
apksigner
: https://developer.android.com/studio/command-line/apksigner- Android Gradle Plugin: https://developer.android.com/studio/releases/gradle-plugin
- Gradle: https://docs.gradle.org/current/userguide/userguide.html
Clover example of apksigner
apksigner
This is an example for using the apksigner
to enable v1 signing scheme, disable v2 and v3 signing schemes, and save the signature file with a name you designate. This example is for illustration purpose only. See the Android developers apksigner
documentation for more information.
$ apksigner sign --ks test-release.jks --v1-signing-enabled=true --v2-signing-enabled=false --v3-signing-enabled=false --v1-signer-name yourname/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.
Updated 3 months ago