Create and batch import HTML5 offline packages - Mobile Platform as a Service - Alibaba Cloud - Mobile Platform as a Service

Create an HTML5 offline package by configuring basic settings, client version targeting, and download behavior — either one at a time or in bulk.

Prerequisites

Before you begin, ensure that you have:

Configured the HTML5 offline package settings on the Configuration Management page. For details, see Configure an offline package.

How it works

Two creation methods are available:

Single package: Configure and upload one offline package through the console form.
Batch import: Upload multiple .zip files at once to create packages in bulk — useful when releasing several H5Apps simultaneously.

When you upload a package for an H5App for the first time, select a resource package type. This selection is permanent — it cannot be changed later, and each H5App supports only one package type.

Procedure

Create a single offline package

In the left navigation pane, choose Mobile Delivery Service > Offline package management.
On the Offline Package Management page, click Create an HTML5 App. Skip this step if you have already created an H5App.
In the Create an HTML5 App window, enter the HTML5 App ID and HTML5 App name, then click OK. Skip this step if you have already created an H5App.
Important
- The H5App ID must be an 8-digit number.
- The IDs 20000196, 66666692, 68687029, and 68687209 are reserved by the software development kit (SDK). Do not use them to avoid conflicts.
- Do not use an H5App ID that starts with 666666 or 20000.
Select the H5App from the list, then click Add an offline package on the right.
In the Basic information section, configure the following parameters:
- Resource package type: Select Global resource package or Normal resource package.
  
  Note
  If you use a global resource package, rename the second-level directory inside the package to mcube-prod.mpaascloud.com. Without this, the real-time release acceleration feature will not work.
- HTML5 app version: Enter the version number of the offline package — for example, 1.0.0.1.
- File: Upload the offline package in .zip format.
- Client version: Select the target client platform (Android, iOS, or both) and set the version range. Only clients within the specified range receive the offline package.
  Note
  - At least one client platform is required. If you select both Android and iOS, both must use the same strategy for the maximum version — either both left blank (system default) or both set to the same value.
  - Leave the maximum version blank to support all future client versions. Setting a specific maximum version risks breaking delivery if your app is upgraded beyond that version.
  - The iOS client version must be lower than the value of the Product Version field in the project's info.plist file.
In the Configuration information section, configure the following parameters:
- URL of main entrance: Optional. The homepage URL of the offline package.
  
  Note
  Enter the full path — for example, /www/index.html, where /www is your second-level directory name.
- Virtual domain: Pre-filled automatically from the value you entered during offline package configuration.
- Extended information: Optional. Enter page loading parameters as key-value (KV) pairs separated by commas.
  
  Use this field to set a per-package request interval, which controls how frequently the client checks for package updates.
  - Single package: Enter {"asyncReqRate":"1800"} to apply a request interval only to this package, where 1800 is the interval in seconds. The range is 0–86400 seconds (0–24 hours). Setting 0 removes the interval limit.
  - Global: Set the interval in client code to apply it across all offline packages. For details, see Quick Start and Quick start.
- Time for download: Select when the client downloads the offline package.
  - Wi-Fi only: The package downloads automatically in the background only when the device has a Wi-Fi connection.
  - All networks: The package downloads on any network, including mobile data. Use this option with caution — it consumes users' mobile data without prompting them.
- Time of installation: Select when the package installs after download.
  - Not preload: The package installs only when the user opens the offline package for the first time.
  - Preload: The package installs automatically as soon as it finishes downloading.
Select the I confirm the above information is accurate checkbox, then click Submit.

Import offline packages in bulk

Batch import lets you create multiple offline packages in a single operation, which is faster than creating packages individually and reduces the risk of configuration errors.

Two behaviors apply automatically after import:

If the H5App for an imported package does not exist, a new H5App is created automatically.
If the H5App already exists, the imported package is added to it.

In the left navigation pane, choose Mobile Delivery Service > Offline package management, then click Batch import HTML5 app.
In the Batch import HTML5 app window, upload the offline package files (.zip).
Note
- The total upload size cannot exceed 300 MB, and the number of packages cannot exceed 100.
- Each file must be named with the corresponding 8-digit offline package ID.
On the import results page, click Edit in the Operation column for each package to review and update its basic information. For a description of each field, see Create a single offline package.

Version numbers are assigned automatically on import:
- If the H5App does not yet exist, the version defaults to 0.0.0.1.
- If the H5App already exists, the version is set to the next increment after the highest existing version.
After editing all packages, select the The information can't be modified after submission checkbox and click Submit. If validation passes, the packages appear on the Offline Package Management page. If validation fails, review the error message and correct the affected entries.

What's next

Release an offline package