Apple released iOS 13 on September 19, 2019. Testing revealed changes in system behavior. Apps must be adapted to these changes to prevent functional errors, crashes, and other issues. |
Background
Apple released iOS 13 on September 19, 2019. Testing revealed changes in system behavior. Apps must be adapted to these changes to prevent functional errors, crashes, and other issues.
Before mPaaS was adapted for iOS 13, the mPaaS SDK built with Xcode 10 on iOS 13 devices was affected in one main way: iOS 13 optimized app startup by changing the image loading mechanism. This change could cause system categories to overwrite category methods defined in the SDK. As a result, custom methods might not return the expected results.
Current status
mPaaS, as a set of base libraries, has been adapted for iOS 13 when built with Xcode 10. Because mPaaS is currently adapted only for packaging with Xcode 10, use Xcode 10 for packaging when you submit your app to the App Store. The toolchain for Xcode 11 is not yet complete. As the toolchain matures, mPaaS will release an adapted version for iOS 13 built with Xcode 11.
Upgrade the SDK or components
Upgrade using the plugin
To upgrade the SDK or components using the mPaaS Xcode plugin, you can choose one of the following two methods:
mPaaS module upgrade
mPaaS baseline upgrade
Choose an upgrade method based on your needs. If you:
already use the plugin to manage component dependencies and your current SDK version is 10.1.32, use the mPaaS module upgrade feature to upgrade the modules you use.
do not use the plugin to manage component dependencies, follow these steps to upgrade:
Use the mPaaS module edit feature to select the modules you need.
Use the mPaaS module upgrade feature to upgrade to version 10.1.32.
Upgrade using CocoaPods
Follow these steps to install the latest SDK of version 10.1.32:
Make sure the version number of the mPaaS components in the Podfile is 10.1.32.
Run
pod mpaas update 10.1.32. If a command error is reported, runpod mpaas update --allto update the plugin first, and then run the command again.Run
pod install.
API changes
mPaaS components in version 10.1.32 include an adaptation layer. 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:
Modify your code to use the methods of the intermediate layer (adapter) 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 during future updates.
Handle custom libraries
Components in version 10.1.32 incorporate custom requirements. However, for stability, if your project depends on custom libraries, handle them as follows:
If you are upgrading from an earlier SDK version to 10.1.32, your custom libraries may need to be re-customized for the new version. Join DingTalk group 145930007362 to contact the mPaaS support for confirmation.
If you are already using version 10.1.32, you may only need to update some components. Check the List of libraries updated for iOS 13 adaptation below to determine if your custom libraries are included.
If they are not included, you can continue to use the custom libraries.
If they are included, your custom libraries may need to be re-customized. Join DingTalk group 145930007362 to contact the mPaaS support.
List of libraries updated for iOS 13 adaptation
mPaaS
MPDataCenter
APMultimedia
BEEAudioUtil
BeeCapture
BeeCityPicker
BeeMediaPlayer
BeePhotoBrowser
BeePhotoPicker
NebulaAppBiz
NebulaBiz
NebulaSDKPlugins
APConfig
AntUI
NebulaSDK
TinyAppCommon
MPPromotion