mPaaS support for multiple CPU architectures

If your application only needs armeabi support, update the SDK to version 10.1.68.21 or later. No other changes are required.

Update the configuration

Overall compatibility

• Native AAR and Portal & Bundle connection types

• armeabi, armeabi-v7a, and arm64-v8a architectures

• targetSdkVersion 26 to 29

• Android 11 is supported.

Publishing on Google Play

If your application uses the mPaaS location component or the map feature in miniapps and needs to be published on Google Play, remove the mPaaS built-in AMAP SDK and replace it with a Google Play-compliant AMAP SDK version. For details, see the following topics:

• Resolve AMAP location conflicts

• Resolve AMAP map conflicts

Update the Gradle configuration

Native AAR

Update the Gradle version to 5.0 or later. Version 6.2 is recommended. If a later version fails to compile, use version 6.2.

distributionUrl=https\://services.gradle.org/distributions/gradle-6.2-all.zip

Portal & Bundle

Update the Gradle version to 5.0 or later. Version 6.2 is recommended. If a later version fails to compile, use version 6.2.

distributionUrl=https\://services.gradle.org/distributions/gradle-6.2-all.zip

Update the Android Gradle Plugin (AGP) version:

For Portal & Bundle, modify the build.gradle file in the root directory of the Portal project and each Bundle project.

classpath 'com.alipay.android:android-gradle-plugin:3.5.18'
classpath 'com.android.tools.build:gradle:3.5.3' // Minimum version: 3.5.0

Generate an APK

Set the CPU architecture

• For native AAR, set the architecture in the build.gradle file of the main project module.

• For Portal & Bundle: To generate an APK, set the architecture in the build.gradle file of the main Portal project module. To generate a Bundle, set the architecture in the build.gradle file of the main Bundle project module.

Set `abiFilters` as follows:

ndk {
    abiFilters "armeabi", "armeabi-v7a", "arm64-v8a"
}

Compile

No special configuration is required. Compile as usual.

Regression testing

Perform full regression testing on the APK for each architecture. Focus on the following components, if you use them:

Component	Validation item
Mobile Gateway	Whether RPC calls succeed after signature verification is enabled. For more information, see Gateway management features. Whether RPC calls succeed after data encryption is enabled.
Hotpatching	Hotpatching is effective.
Scan	Whether scanning with the standard UI succeeds. Whether the standard UI correctly opens the photo album, takes photos, and previews images. If you use a custom UI, you must adapt to the new interfaces to ensure successful QR code scanning.
Unified Storage	Encrypted database storage works correctly. Encrypted file storage works correctly.
Share	Sharing to Sina Weibo and QQ succeeds.
OCR	Whether OCR detection works correctly.
Audio and video	Audio and video calls work correctly.