DocsICP FilingConsole
官方文档
首页

mPaaS 10.1.68 upgrade guide

更新时间：
复制 MD 格式
产品详情
我的收藏

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 the mPaaS Xcode Extension

Prerequisites

Ensure that the mPaaS Xcode Extension is updated to version 1.1.0 or later. To update the mPaaS Xcode Extension, see Update the mPaaS Xcode Extension.

Procedure

  1. In the Xcode menu, click Editor > mPaaS > Edit Project to open the mPaaS Xcode Extension.

    • If you have already integrated baseline version 10.1.68, select the Update Product Set option to upgrade to the latest product set.

    • If you are using a baseline version other than 10.1.68, select the Upgrade Baseline option. Set the baseline version to 10.1.68. The upgrade may take a long time. Do not close the plugin window during the process.

  2. After the update or upgrade is successful, the plugin will show the project's SDK version as 10.1.68.

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, Mini Program, and Hotpatching components, read the following instructions carefully:

  • For information about upgrading the H5 Container and offline packages, see the H5 Container 10.1.60 upgrade guide.

  • For information about upgrading Mini Programs, see the Mini Program upgrade notes.

  • If your current baseline version is earlier than 10.1.60, you must also upgrade the hotpatching library to version 10.1.68. You can obtain the hotpatching library from the helpdesk. To contact the mPaaS helpdesk, join the DingTalk group 145930007362.

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

  • Note the changes in the configuration category and the info.plist file for each mPaaS component in your project.

  • 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.

  • iOS hotpatching is for Apsara Stack only. For more information, contact mPaaS technical support.

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.

Previous：Privacy permissionNext：Adapt mPaaS 10.1.68 for Xcode 13