mPaaS 10.2.3.63 adds full compatibility with Android 16. Upgrade your SDK, switch to the mPaaS kernel, and verify any custom libraries to keep your app running correctly on Android 16 devices.
Google released Android 16 Beta 4 in April 2025. mPaaS 10.2.3.63 has been tested for full compatibility with this release.
Upgrade the SDK
Use the mPaaS plugin to upgrade the mPaaS SDK.
If your current baseline is 10.2.3, upgrade to version 10.2.3.63 or later. See 10.2.3 baseline versions.
If your current baseline is 10.1.68 or earlier, first upgrade to 10.2.3 and then update to 10.2.3.63 or later. See the mPaaS 10.2.3 Upgrade Guide.
Kernel
Upgrade the kernel component in your mPaaS baseline to the mPaaS kernel to ensure compatibility with Android 16 and future Android versions.
System kernel downgrade
Apps that are not upgraded to the mPaaS kernel automatically fall back to the Android system kernel when running on Android 16 or later.
Regression testing
Switching kernels — whether to the mPaaS kernel or falling back to the system kernel — can change browser behavior. Run regression tests on any services that depend on the kernel, such as H5 containers and Mini Programs.
Handling custom libraries
If your dependencies include custom libraries, follow these steps:
If you are upgrading from an earlier baseline, such as 10.1.68, to 10.2.3, you may need to rebuild your custom libraries. Search for DingTalk group ID 145930007362 to join the group and consult the mPaaS helpdesk.
If you are already on version 10.2.3, check whether your custom libraries appear in the List of libraries updated for Android 16 below.
If your custom libraries are not in the list, no action is required.
If your custom libraries are in the list, they may need to be rebuilt. Search for DingTalk group ID 145930007362 to join the group and consult the mPaaS support.
List of libraries updated for Android 16
com.mpaas.myweb:mpaasmywebapi-build
com.mpaas.myweb:mpaasmyweb