All Products
Document Center

Mobile Platform as a Service:mPaaS 10.1.60 upgrade guide

Last Updated:May 24, 2023

About mPaaS 10.1.60

  1. The 10.1.60 baseline now supports WKWebView APIs. For details, see Version 10.1.60 is adapted to WKWebView. Since App Store no longer accepted new apps using UIWebView from April 2020, updates to these apps were no longer accepted from December 2020. For more information, see Apple's official statement. Therefore, developers need to replace UIWebView with WKWebView.

  2. The 10.1.60 baseline has been adapted to iOS 13 and Xcode 11. For more information, see mPaaS 10.1.60 is adapted to iOS 13.

  3. The mini program component has been added to the 10.1.60 baseline. The official version of the mini program has a complete set of APIs, with greatly improved stability and compatibility. For more information about upgrading mini programs, see Mini program upgrade guide. For more information about the debugging, preview, and release of new mini programs in the integrated development environment (IDE), see Develop mini programs.

  4. The 10.1.60 baseline dramatically optimizes HTML5 containers, provides a more simplified integration process, and significantly improves its compatibility and stability. For more information about upgrading HTML5 containers and offline packages, see HTML5 container upgrade guide.

  5. Mobile Content Delivery Platform (MCDP) has been added to the 10.1.60 baseline. MCDP provides the ability to personalize advertisements within an app, supports personalized advertisement placement for targeted groups, and helps app operators to reach users accurately and timely. For details, see MCDP.

  6. The overall compatibility and stability of the 10.1.60 baseline components have been greatly improved, and the features have also been significantly improved. For more information about the release notes, see iOS SDK release notes.

  7. The 10.1.60 baseline no longer supports iOS 8.

mPaaS 10.1.60 upgrade guide

Use CocoaPods for upgrade


The CocoaPods mPaaS plug-in has been installed.

  • If you have not installed the CocoaPods mPaaS plug-in, execute the following script on the terminal to install the plug-in.

      sh <(curl -s
  • If you have installed the CocoaPods mPaaS plug-in, run pod mpaas update --all to upgrade the plug-in. For more information about using the CocoaPods mPaaS plug-in, see Integrate by using CocoaPods based on the native framework.

  1. In Podfile, change the SDK version to

  2. Run pod mpaas update 10.1.60 to install the latest SDK for the 10.1.60 baseline.

  3. Run pod install or pod update as needed to upgrade the SDK to version 10.1.60 in the project.

Subsequent steps

If you encounter the following error when integrating CocoaPods:

Invalid `Podfile` file: [!] No mPaaS_Nebula : 10.1.60-beta found !!! Check name & version in Podfile.

Perform the following steps:

  1. Run gem list | grep 'mPaaS' to view the CocoaPods plug-in version, as shown in the following figure.

  2. If the CocoaPods plug-in version is earlier than 0.9.5, execute the following script to reinstall the plug-in.

    sh <(curl -s

Component usage and upgrade guide

In the 10.1.60 baseline, the accessibility and usability of HTML5 containers and mini programs have been greatly improved. If you have used these components, read the following instructions in detail.

Component API changes

Starting from the 10.1.32 baseline, an adaptation layer has been added to the mPaaS component. If your baseline is not using adaptation-layer APIs, read mPaaS 10.1.32 is adapted to iOS 13 first.

We recommend that you use the APIs of the adaptation layer after you upgrade the SDK. For details, see the following upgrade instructions for different components:


    We strongly recommend that you modify the code and use middle-layer (adapter) methods instead of directly using underlying methods, because certain underlying methods may be modified or discarded in future versions. You may need to take lots of time adapting them in future updates if you continue to use them.

      Handle custom libraries

      Each component of the 10.1.60 baseline is integrated with customization requirements. However, if your previous dependencies include customization libraries and you are upgrading from an earlier version (such as 10.1.32) to 10.1.60, your customization libraries may need to be re-customized based on the new version. In this case, you can submit a ticket or contact mPaaS technical support staff for confirmation.