All Products
Search

This Product

    Mobile Platform as a Service:mPaaS 10.1.68 upgrade guide

    Document Center

    Mobile Platform as a Service:mPaaS 10.1.68 upgrade guide

    Last Updated:Feb 03, 2026

    mPaaS 10.1.68 release notes

    1. Starting with baseline 10.1.68, UIWebView is deprecated and only WKWebView is supported. For more information, see Adapt mPaaS to WKWebView. The App Store stopped accepting new apps that use UIWebView in April 2020. It will stop accepting updates for existing apps that use UIWebView in December 2020. You should upgrade to baseline 10.1.68 and adapt your application for WKWebView as soon as possible.

    2. This version supports building and packaging static libraries with Xcode 11, ensuring compatibility for development.

    mPaaS 10.1.68 upgrade guide

    Upgrade using CocoaPods

    Prerequisites

    The CocoaPods mPaaS plugin has been installed.

    • If you have not installed the CocoaPods mPaaS plugin, run the following script in the terminal to install it.

        sh <(curl -s http://mpaas-ios.oss-cn-hangzhou.aliyuncs.com/cocoapods/installmPaaSCocoaPodsPlugin.sh)

    • If you have already installed the CocoaPods mPaaS plugin, run the pod mpaas update --all command to upgrade the plugin. For more information about how to use the CocoaPods mPaaS plugin, see Integrate with a native framework using CocoaPods.

    Procedure

    1. In the Podfile, change the SDK version to 10.1.68.2

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

    3. If necessary, run pod install or pod update to complete the project upgrade to 10.1.68.

    What to do next

    If an error similar to the following occurs during CocoaPods integration:

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

    You can try the following steps to resolve the issue:

    1. Run the gem list | grep 'mPaaS' command to check the CocoaPods plugin version, as shown in the following figure.cocoapod 故障排查

    2. If the CocoaPods plugin version is earlier than 0.9.5, run the following script to reinstall the plugin.

    sh <(curl -s http://mpaas-ios.oss-cn-hangzhou.aliyuncs.com/cocoapods/installmPaaSCocoaPodsPlugin.sh)

    Component upgrade guide

    If your current baseline version is earlier than 10.1.60 and you have integrated the H5 Container and Mini Program components, read the following instructions carefully:

    Component API changes

    An adaptation layer has been included in mPaaS components since baseline 10.1.32. If the baseline you are using does not use the adaptation layer API, see Adapt mPaaS 10.1.32 to iOS 13 before you proceed.

    After you upgrade the SDK, use the APIs of the adaptation layer. For more information, see the notes on upgrading from earlier versions in the following component documents:

    Note

    • Modify your code to use the intermediate layer (adapter) methods instead of the underlying methods. Some underlying methods may be changed or deprecated in future versions. If you continue to use them, you may need to spend more time on adaptation in future updates.

    Handling custom libraries

    The components of baseline version 10.1.68 incorporate customized requirements. However, if your dependencies previously included custom libraries and you are upgrading from an earlier SDK version, such as 10.1.32, to version 10.1.68, your custom libraries may need to be re-customized for the new version. For consultation, search for and join the DingTalk group 145930007362.

    Share component

    The third-party SDKs in the Share component of version 10.1.68 have been upgraded. These include the WeChat SDK, Weibo SDK, and QQ Connect SDK. The latest versions for WeChat and QQ sharing add the Universal Link feature. You must adapt your application to the new SDKs. This adaptation includes the following steps:

    1. Update the application configuration information on the corresponding third-party platform. You can find this information in the application management section of your developer account on that platform. For specific adaptation methods, see the documentation provided by the platform.

    2. For WeChat sharing, add the "universalLink" field to the configuration information of the mPaaS Share component. Set the value of this field to the Universal Link address of your application.