After you generate a signed APK, you can upload the APK to your Clover app from the Developer Dashboard.
- The package name doesn't begin with
com.clover.(Only Clover-owned apps can begin with
android:minSdkVersionattribute in your
AndroidManifest.xmlhas a value of 17 or less.
android:versionCodeattribute in your
AndroidManifest.xmlis greater than the version code of any APK you've already uploaded.
- The certificate's signature algorithm must be at least
SHA1withRSA, 2048-bit key(RSA2048 with SHA-256). This can be verified with the following command:
jarsigner -verify -verbose <filename>.apk.
- The APK is signed with the same key you used to sign the first APK you uploaded.
- The APK is signed in release mode.
- The APK is signed with only the V1 signature scheme (Jar Signature). The V2 signature scheme is not supported.
- The signature file is saved as
- The size of the APK file doesn't exceed 120 MB.
The package name is selected from the first APK you upload for an app. You can't change the package name after this. New versions of the APKs must have the same package name and an incremented
versionCode (set in your
build.gradle and reflected in the app's manifest). Check the package attribute in your manifest file carefully before uploading the APK.
- On Developer Dashboard side-nav, click the app name to expand the menu options.
- Click App Releases.
- On the App Releases page, click UPLOAD APK.
Note that you also upload your APK from the App Settings modal.
- On the New Public Release modal that appears, click CHOOSE APK.
- Locate the APK file you want to upload and either drag the APK file to the modal or select the file and click Open.
- In the Release Notes field, enter release notes for your uploaded APK.
Release notes help Clover merchants learn about new features and updates in a new version of your Android app.
- Click Upload.
The uploaded APK is available in the Releases table.
Updated 4 months ago