zec
/
secant-android-wallet
mirror of https://github.com/zcash/secant-android-wallet.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
secant-android-wallet/docs/Deployment.md

2.6 KiB
Raw Blame History

Signing

To create a release build, signing must be configured. The following Gradle properties must be set:

  1. ZCASH_RELEASE_KEYSTORE_PATH
  2. ZCASH_RELEASE_KEYSTORE_PASSWORD
  3. ZCASH_RELEASE_KEY_ALIAS
  4. ZCASH_RELEASE_KEY_ALIAS_PASSWORD
  5. Run ./gradlew :app:assembleRelease to create a signed release APK, which can be tested and easily installed on an emulator or test device. Note that this APK cannot be deployed, because Google Play requires deployment in AAB format. APK, however, is easier to manage for manually creating a build for testing.

Note that although these are called "release" keys, they may actually be the "upload" key if Google Play Signing is being used.

Deployment

After signing is configured, it is possible to then configure deployment to Google Play.

Automated Deployment

Automated deployment to Google Play is configured with custom Google Play publishing Gradle task. To perform a deployment with this task:

  1. Configure a Google Cloud service account and API key with the correct permissions
  2. Configure a Google Play Publishing API key in Google Cloud console
  3. Configure Gradle properties
    1. ZCASH_GOOGLE_PLAY_SERVICE_ACCOUNT_KEY - Set the Google Play Service Account enabled in the Google Cloud console
    2. ZCASH_GOOGLE_PLAY_PUBLISHER_API_KEY - Set the Google Play Publish API enabled in the Google Cloud console
    3. ZCASH_GOOGLE_PLAY_DEPLOY_TRACK - Set to internal or alpha
    4. ZCASH_GOOGLE_PLAY_DEPLOY_STATUS - Set to draft or completed
  4. Run the Gradle task ./gradlew :app:publishBundle

For more information about proper automated deployment setup, see Google Play publishing Gradle task documentation and related gradle.properties attributes.

Note that the above instructions are for repeat deployments. If you do not yet have an app listing, you'll need to create that manually.

Note that the artifacts can be manually saved from their output directory under the app/build directory

Manual Deployment

To manually deploy a build of the app

  1. Configure Gradle properties
    1. ZCASH_VERSION_CODE - Set to the integer version code of the app. A simple monotonically increasing number is recommended.1
    2. ZCASH_VERSION_NAME - Set to a human-readable version number, such as 1.0.1.
  2. Run the Gradle task ./gradlew :app:bundleRelease
  3. Collect the build artifacts under app/build and manually deploy them through the Google Play web interface