About the mPaaS 10.1.60 official version
The 10.1.60 baseline is compatible with Android 10.
The 10.1.60 baseline includes the official version of the Mini Program component. This version provides more comprehensive APIs and significantly improves stability and compatibility. For more information about Mini Program upgrades, see Mini Program Upgrade Guide. For more information about new features in the Mini Program IDE, such as debugging, previewing, and publishing, see Mini Program IDE.
The 10.1.60 baseline significantly optimizes the H5 container. It provides a simplified integration process and enhanced capabilities. It also offers major improvements in compatibility and stability. For more information about H5 container and offline package upgrades, see H5 Container Upgrade Guide.
The 10.1.60 baseline adds support for push notifications on OPPO and vivo channels to the Mobile Push component.
The 10.1.60 baseline introduces management features for the Social Share component and provides a simplified integration process. For more information about the Social Share upgrade, see Migrate to the 10.1.60 baseline.
The 10.1.60 baseline introduces the Smart Delivery component. Smart Delivery lets you deliver personalized ads within your application to targeted user groups. This feature helps app operators reach users with precision and in a timely manner. For more information, see Smart Delivery.
The 10.1.60 baseline significantly improves the overall compatibility, stability, and features of its components. For detailed release notes, see Android SDK Release Notes.
mPaaS 10.1.60 official version upgrade guide
Procedure
Upgrade the Android Studio mPaaS plugin to v2.19123015 or later. For more information about updating the mPaaS plugin, see Update the mPaaS plugin.
In your Android Studio project, go to mPaaS > Baseline Upgrade. Select 10.1.60 and click OK.
After the upgrade, confirm that the "base_line" field in mpaas_packages.json is set to 10.1.60.
The procedure for upgrading from the 10.1.60-beta baseline to the official version is the same.
Component usage upgrade guide
The H5 Container, Mini Program, and Social Share components in the 10.1.60 baseline have major changes to their integration and usage. If you use these components, review the following instructions carefully:
For more information about H5 container and offline package upgrades, see H5 Container Upgrade Guide.
For more information about Mini Program upgrades, see Mini Program Upgrade Guide.
The integration method for the Social Share SDK has been updated. For more information about the Social Share component upgrade, see Migrate to the 10.1.60 baseline.
Note:
Starting with version 10.1.60, the Share SDK is managed by the mPaaS plugin. To install the Share component, see Migrate to the 10.1.60 baseline.
If you do not use the plugin to integrate the Share SDK, you will not receive timely updates for Share SDK upgrades or bug fixes.
Component API changes
Starting with the 10.1.32 baseline, mPaaS components include an adapter layer. We recommend that you use the APIs that include this adapter layer. For more information, see the upgrade notes for previous versions in the following component documents:
Mobile Analysis:
A new adapter has been added to simplify usage. For more information, see Custom Event Logs.
Some APIs are deprecated. Use the new APIs to prevent compilation failures. For more information, see Mobile Analysis.
Mobile Push: A new adapter has been added to simplify usage. For more information, see Mobile Push.
Mobile Sync: A new adapter has been added to simplify usage. For more information, see Mobile Sync.
Hotpatching: A new adapter has been added to simplify usage. For more information, see Hotpatching SDK.
Upgrade: A new adapter has been added to simplify usage. For more information, see Upgrade.
Configuration Switch: A new adapter has been added to simplify usage. For more information, see Configuration Switch.
H5 Container:
A new adapter has been added to simplify usage. For more information, see H5 Container SDK 10.1.32.
The container configuration method has changed. If you upgrade from version 10.0.18, you must use the new container configuration method. Otherwise, your container configuration will not take effect. For more information, see Container Configuration 10.1.32.
For changes in the 10.1.60 baseline, see the Upgrade Guide.
Mini Program:
First, upgrade the H5 container.
For information about upgrade changes, see the Upgrade Guide.
We recommend that you modify your code to use the adapter layer methods instead of the underlying methods. Some underlying methods may be changed or deprecated in future versions. If you continue to use the underlying methods, adapting to future updates may require additional effort.
Handling custom dependencies
Check the dependency configurations in all build.gradle files. Check for any bundle dependencies for mPaaS components. If you have such dependencies and are upgrading from an earlier software development kit (SDK) version, such as 10.1.32, to 10.1.60, you may need to rebuild your custom library based on the new version. Otherwise, you may encounter compatibility issues. If you are unsure whether a rebuild is necessary, submit a ticket or contact mPaaS support.