Adapt mPaaS 10.1.68 for Android 11

Background

Google officially released Android 11 on September 9, 2020. mPaaS was adapted for Android 11 in baseline 10.1.68. Versions 10.1.68.14 and later are compatible with Android 11. Before this adaptation, the mPaaS SDK was affected on Android 11 devices: the H5 container could not start the UC kernel.

Upgrade SDK/components

You can use the mPaaS plugin to upgrade the mPaaS SDK or components.

• If you are already using baseline 10.1.68, you can simply upgrade to the latest version. For more information, see the 10.1.68 Release Notes.

• If you are using baseline 10.1.60 or an earlier version, you must upgrade to 10.1.68 and then update to the latest version. There are no plans to support Android 11 on mPaaS 10.1.60 or earlier versions.

Update hotpatching configuration

If you use hotpatching on a baseline earlier than 10.1.68.14, you must update the hotpatching whitelist configuration for Android 11 compatibility. For more information, see Whitelist configuration file rules.

Handling custom libraries

Version 10.1.68 incorporates custom requirements into its components. However, if your dependencies include custom libraries, you must handle them as follows:

• If you upgrade to version 10.1.68 from an earlier SDK version, such as 10.1.60, your custom libraries may need to be re-customized for the new version. For assistance, search for the group number 145930007362 and join the DingTalk group.

• If you already use version 10.1.68 and only update some components, check the List of libraries updated for Android 11 below to see if your custom library is included.

  • If it is not included, you can continue to use the custom library.

  • If it is included, your custom library may need to be re-customized. For assistance, search for the group number 145930007362 and join the DingTalk group.

List of libraries updated for Android 11

• nebulaappproxy

• nebulauc