All Products
Search
Document Center

Mobile Platform as a Service:Use hotpatch

Last Updated:Feb 11, 2026

Hotpatch fixes live issues with code changes without releasing a new version. Hotpatch management is the configuration backend used to fix urgent client issues. In this backend, you can create release tasks and configure multi-dimensional hotpatches.

About this task

On the Hotpatch Management page, you can complete the following tasks:

  1. Add a hotpatch: Add a hotpatch package to the mPaaS console.

  2. Release a hotpatch package: Following best practices, releasing a hotpatch package involves three stages: whitelist canary release, time window canary release, and official release.

    Note

    If a code issue occurs during releasing, you can perform a rollback.

  3. Manage a release task: Managing release tasks includes modifying, pausing, and ending them.

For Android client hotpatching, each version can have only one hotpatch package. If a version of an Android client has two issues, you must first combine the two hotpatch packages into one on your local machine and then upload the combined package.

Add a hotpatch

  1. Log on to the mPaaS console. In the navigation pane on the left, choose Mobile Delivery Service > Hotpatch Management to go to the hotpatch resource list page.

  2. Click Add hotpatch resource to add a new hotpatch resource. In the Add hotpatch resource window that appears, complete the hotpatch configuration.

    Note

    For the Android platform, Target Version in the Add hotpatch resource window refers to the version number of the Portal package.

  3. In the hotpatch resource list, click the expand button () to the left of a hotpatch to view its release tasks.

Release a hotpatch package

  1. In the hotpatch resource list, click Create a release task to the right of a hotpatch to add a new release task.

  2. In the Create a release task window, configure the following settings.

    image

    • Task type: Includes Official task and Rollback task.

      • Official task: Apllicable to normal hotpatch packages.

      • Rollback task: Roll back the release when a code defect occurs when releasing a hotpatch package. The release type for Rollback task is fixed to Official release.

    • Release type: Includes Gray release and Official release.

    • Release model: For Gray release only. Includes Whitelist and Time window.

      • If choosing Whitelist, you need to choose the preconfigured whitelist in the Whitelist configuration field. For details about whitelist configuration, see Whitelist management.

      • If choosing Time window, you need to set End time and Users count.

    • Advanced rule: Set advanced rules to filter users by various conditions, such as city, device model, and network. Advanced rules are configured in Resource Configuration Management.

  3. Click OK to create the task.

Manage a release task

In the hotpatch resource list, find the release task for a specific hotpatch resource. You can then click the Modify, Pause, or End button to the right of the task to modify, pause, or end it.

  • Modify a task

  • Pause a task: A paused task can be resumed.

    image

  • End a task: An ended task cannot be modified or resumed.