Mobile Platform as a Service:Adapt mPaaS for 16 KB

mPaaS adapted its core components for 16 KB page size in the 10.2.3.global international baseline. To support 16 KB, update the SDK to the latest 10.2.3.global international baseline version using the mPaaS plugin, then adapt your app and run regression tests as described below.

16 KB adaptation

Kernel

If you integrated the kernel component, follow the Integrate mPaaS Kernel guide for 16 KB compatibility. Use the following 16 KB-compatible versions for all kernel-related dependencies.

Mini program

Nebula mini program

If you integrated the legacy mini program, upgrade to the new mini program container by following the Quick Start guide for 16 KB compatibility.

Mriver mini program

The following APIs are not yet 16 KB-compatible. Do not use them.

• Canvas 2.0-related APIs and components

• Camera-related APIs

Amap location and map

The Amap Location and Amap Map SDKs in the mPaaS baseline are not 16 KB-compatible. Check whether your app integrates any of these components:

• Mriver Mini Program

• Native mini program (private cloud)

• Mobile Content Delivery Platform

These components depend on the Amap Location or Amap Map SDK. If you do not use location or map features, remove the related dependencies. If you use these features, manually import a 16 KB-compatible version from the official Amap website.

Remove Amap SDK dependencies

Add this configuration to your main module's build.gradle:

configurations.all {
    exclude group:'com.mpaas.group.amap', module: 'amap-build'
    exclude group:'com.alipay.android.phone.thirdparty', module: 'amap3dmap-build'
    exclude group:'com.alipay.android.phone.mobilecommon', module: 'lbs-build'
}

Use the location component

If you integrated the location component, remove the amap-build and amap3dmap-build dependencies as described above, but keep lbs-build.

Import the Amap SDK

Import the latest Amap SDK or another 16 KB-compatible SDK and call the AutoNavi Privacy API.

Remove incompatible components

The following components are not yet 16 KB-compatible. If your app uses them, temporarily remove their dependencies from your build.gradle. Identify them by name or by the .so files they contain:

Ant Cube Card (Magic cube card)

• libantcrystal.so

• libnative-cube.so

• libnative-v8bridge.so

• libcubedebug.so

• libiwasm.so

Video player

• libantplayer-2.0-4x.so

• libantplayer-netcache.so

• libantplayerinf-2.0-4x.so

• libijkffmpeg4x.so

Intelligent Dual-Recording, Intelligent Dual-Recording - Flow Orchestration

• libsls_producer.so

• libmnnface.so

• libmnnhanddetect.so

• libneonuijni.so

• libiwasm.so

Human-Machine Dual-Recording

• libAntAudio_VQE.so

Mobile Gateway Service - H2 plugin, RTMS, and edge intelligence

• libBifrost.so

• libzstd.so

F2 Chart Engine

• libf2.so

Edge Intelligence

• liboasis_sdk.so

Regression testing

Run full regression tests on devices with a 16 KB page size.

If you use the following components, test their features during regression:

Components that cannot be tested

Social media apps like WeChat have not yet adapted for 16 KB and may crash on 16 KB devices. As a result, mPaaS cannot test the sharing component for 16 KB compatibility.