Mobile Platform as a Service:mPaaS baseline release overview

Upgrade impacts

• IOS and Android dual-end wireless bodyguards will stop maintenance from April 1, 2024. At that time, the generation and related use capabilities of wireless bodyguard pictures will no longer be provided. The wireless bodyguard SDK functions used by the original App will not be affected for the time being (if there are any problems, please switch to blue shield). For newly connected mPaaS App and the original App, please refer to the document mPaaS wireless bodyguard switching blue shield.

• Starting from Android 10.2.3.38 (effective from November 30, 2023), the mPaaS push service adapts to the push channel of Honor vendors. In order not to affect the reach of users of Honor new machines, we recommend that you upgrade the baseline to 10.2.3.38 or later as soon as possible. For more information, see mPaaS 10.2.3 adapts to Honor vendors.

• Starting from Android 10.2.3.33 (effective October 12, 2023), mPaaS is fully adapted to Android 14. This adaptation is only performed on the 10.2.3 baseline. To facilitate subsequent upgrades, we recommend that you upgrade to the 10.2.3 baseline as soon as possible. For more information, see mPaaS 10.2.3 for Android 14.

• Since September 17, 2023, Google Play has updated the application review scanning rules, which will incorrectly identify some codes in the mPaaS SDK as Taobao windvane SDK, resulting in the application rejection. mPaaS has removed the relevant code from the 10.2.3.32 baseline. If you want to publish Google Play, please upgrade to 10.2.3.32 or later as soon as possible.

• The built-in Xiaomi push SDK in Android 10.2.3.24 - 10.2.3.27 may cause application installation or upgrade exceptions. This issue has been fixed in the 10.2.3.28 baseline version. If you have connected to the 10.2.3.24 - 10.2.3.27 baseline and used the Xiaomi push component, please upgrade to 10.2.3.28 or later as soon as possible.

• Starting with iOS 10.2.3.19 (effective April 2023), mPaaS will be fully adapted to Xcode 14. This adaptation is only performed on the 10.2.3 baseline. The 10.1.68 baseline is no longer adapted. To facilitate subsequent upgrades, we recommend that you upgrade to the 10.2.3 baseline as soon as possible. For more information, see Adapt to Xcode14 10.2.3 mPaaS.

• MPaaS has newly released Android 10.2.3 baseline, adding a number of new components such as SSL, terminal environment detection, threat perception, sweep AI, ID Verification, intelligent double recording, Rubik's Cube card, terminal intelligence, etc. It supports targetSdkVersion 30. The cpu architecture only supports armeabi-v7a and arm64-v8a , and no longer supports armeabi. For more information, see mPaaS 10.2.3 Upgrade Guide.

• mPaaS newly released iOS 10.2.3 baseline, fully adapted to iOS 16, added multiple new components such as SSL, terminal environment detection, threat perception, ID Verification, etc., and upgraded wireless bodyguard V6 pictures. For details, see Use of mPaaS 10.2.3 and Adaptation to iOS 16.

• Since iOS 10.1.68.53 (effective as of September 8, 2022), mPaaS is fully compatible with iOS 16. To ensure functionality and stability, we recommend that you upgrade mPaaS to 10.1.68.53 or later as soon as possible. For more information, see mPaaS 10.1.68 adapts to iOS 16.

• Since iOS 10.1.68.47 (effective as of April 2022), mPaaS is fully adapted to Xcode 13. This adaptation is only performed on the 10.1.68 baseline. To facilitate subsequent upgrades, we recommend that you upgrade to 10.1.68.47 or later as soon as possible.

• Starting from Android 10.1.68.37 (effective as of September 29, 2021), mPaaS is fully adapted to Android 12. This adaptation is only performed on the 10.1.68 baseline. To facilitate subsequent upgrades, we recommend that you upgrade to the 10.1.68 baseline as soon as possible.

• Since iOS 10.1.68.38 (effective as of September 13, 2021), mPaaS is fully compatible with iOS 15. This adaptation is only performed on the 10.1.68 baseline. To facilitate subsequent upgrades, we recommend that you upgrade to the 10.1.68 baseline as soon as possible.

• Starting from Android 10.1.68.21 (effective January 8, 2021):

  • mPaaS adds support for targetSdkVersion 29. For more information, see mPaaS adaptation targetSdkVersion 29.

  • Since Android 10.1.68.21 (effective as of September 29, 2021), the CPU architecture supports armeabi-v7a and arm64-v8a (including the video function of the small program component arm64-v8a from 10.1.68.22). For more information, see Multi-CPU architecture supported by mPaaS.

• Starting from Android 10.1.68.14 (effective September 17, 2020), mPaaS is fully adapted to Android 11. This adaptation is only performed on the 10.1.68 baseline. To facilitate subsequent upgrades, we recommend that you upgrade to the 10.1.68 baseline as soon as possible.

• Since iOS 10.1.68.17 (effective as of September 14, 2020), mPaaS is fully compatible with iOS 14. This adaptation is only performed on the 10.1.68 baseline. To facilitate subsequent upgrades, we recommend that you upgrade to the 10.1.68 baseline as soon as possible.

• Since Android 10.1.68.10 (effective as of August 5, 2020) and iOS V10.1.68.13 (effective as of August 5, 2020), the mPaaS client will verify the validity of Alibaba Cloud public cloud customer identity. Users who fail the verification will no longer be able to use the capabilities of mPaaS. To ensure that you can continue to use mPaaS smoothly, please retrieve the .config file in the mPaaS console and import it to the project. For more information, see mPaaS user authentication.

• Starting from December 2020, Apple will no longer accept apps that use UIWebview. At that time, apps that use the iOS 10.1.60 series baseline will not pass Apple's review. We strongly recommend that users who use the 10.1.60 series baseline upgrade to the 10.1.68 series baseline.