Skip to main content

Deploying apps to Huawei AppGallery

Abstract

You can deploy your Android apps to Huawei AppGallery via a verified Bitrise Step called Deploy to Huawei App Gallery. The Step can be used to deploy any APK file that you build on Bitrise.

You can deploy your Android apps to Huawei AppGallery via a verified Bitrise Step called Deploy to Huawei App Gallery. The Step can be used to deploy any APK file that you build on Bitrise.

The Step will need:

  • The App ID of the app.

  • The Client ID of the API client.

  • The Key generated for the API client.

To successfully deploy your app to Huawei AppGallery, you need a Workflow that:

  • Builds and signs an APK or AAB file.

  • Includes the Deploy to Huawei App Gallery Step to deploy the app.

To configure deploying with the Deploy to Huawei App Gallery Step:

  1. Manually upload the first APK of the app to Huawei AppGallery using the website interface on AppGallery Connect.

  2. Create a team-level API client on AppGallery Connect.

    huawei_api.png

  3. Open the Workflow Editor on Bitrise.

  4. Go to the Workflow that you want to use for deploying the app.

  5. Add the Deploy to Huawei App Gallery Step after the Steps that build and sign your APK.

    huawei_step.png

  6. Open the Config input group.

  7. Fill in the required inputs.

    • File path: If you used a Step that automatically exports the BITRISE_APK_PATH Environment Variable after building your APK, leave this unchanged. The Android Build Step is such a Step, for example.

    • File name: The unique name of the APK file. This name will be used when uploading to the AppGallery Connect.

    • App ID: The identified can be found in the App information section on AppGallery Connect.

    • Client ID: The API client ID generated on AppGallery Connect.

    • Key: The key generated with the API client on AppGallery connect.

Take a look at the following bitrise.yml file to see an example configuration that uses the Deploy to Huawei AppGallery Step to deploy an app.

workflows:
  deploy:
    steps:
    - [email protected]:
        run_if: '{{getenv "SSH_RSA_PRIVATE_KEY" | ne ""}}'
    - [email protected]: {}
    - [email protected]: {}
    - [email protected]:
        inputs:
        - gradlew_path: "$PROJECT_LOCATION/gradlew"
    - [email protected]:
        inputs:
        - gradle_file: "$GRADLE_BUILD_FILE_PATH"
        - gradle_task: assembleRelease
        - gradlew_path: "$GRADLEW_PATH"
    - [email protected]: {}
    - [email protected]: {}
    - [email protected]: {}
    - appgal[email protected]:
        inputs:
        - huawei_client_id: 'XXX'
        - huawei_client_secret: "$CLIENT_SECRET"
        - huawei_app_id: 'YYY'

Run a build! If all goes well, you should see your app on Huawei AppGallery.

In this section:

A Step is a block of script execution that encapsulates a build task on Bitrise: the code to perform that task, the inputs and parameters you can define for the task, and the outputs the task generates.

An app on Bitrise represents a Git repository that stores source code and has been connected to Bitrise to be able to run builds on it. As such, a Bitrise app isn't necessarily an actual application: it's just the code on which you run builds with Bitrise.

A Workflow is a collection of Steps, Environment Variables, and other configurations. When Bitrise starts a build, it runs one or more Workflows according to the configuration defined in the bitrise.yml file.

The bitrise.yml file stores your entire build configuration for an app. It specifies your stack and the build triggers, and defines the Workflows of the app. When you make changes on the graphical UI of our Workflow Editor, you actually modify the bitrise.yml file.