All Products
Search

This Product

    Mobile Platform as a Service:Adapt mPaaS 10.1.68 for iOS 16

    Document Center

    Mobile Platform as a Service:Adapt mPaaS 10.1.68 for iOS 16

    Last Updated:Feb 05, 2026

    This topic describes the adaptation of mPaaS baseline 10.1.68 for iOS 16 and the required adaptation steps.

    Background

    iOS 16 was officially released in September 2022. Applications must be adapted to its new system features and interfaces. mPaaS has completed the adaptation and testing for iOS 16 beta(8) in baseline versions 10.1.68.53 and later.

    Current status

    As a set of base libraries, mPaaS has completed adaptation and testing for iOS 16 beta(8) for IPA packages built with Xcode 13. If you plan to publish your application on the Apple App Store, use Xcode 13 for packaging.

    The toolchain for Xcode 14 is under improvement. Once the toolchain is ready, mPaaS will release a version adapted for iOS 16 that is built with Xcode 14.

    Upgrade the baseline

    Choose an upgrade method based on your current baseline version.

    Current baseline is 10.1.68

    Upgrade using CocoaPods

    To install the latest SDK of version 10.1.68, perform the following steps:

    1. Ensure that the version of the mPaaS components in your Podfile is set to 10.1.68.

    2. Run pod mpaas update 10.1.68.

      If a command error occurs, run pod mpaas update --all to update the plugin, and then run the command again.

    3. Run pod install --repo-update.

    The current baseline is a custom baseline other than 10.1.68

    Contact your helpdesk or technical support staff for information about which baseline to use.

    Security configuration

    Applications developed on the mPaaS framework that use H5 containers or miniapps often use JSAPIs. To prevent external pages from misusing application information, you must validate URLs when they are opened or used by JSAPIs. This validation ensures that only URLs related to your application's services are loaded. It also lets you restrict the scope and permissions of JSAPI calls for URLs. This practice prevents problems caused by a lack of authentication.

    For more information about authentication methods, see the following documents:

    1. Set JSAPI authentication.

    2. Set a URL whitelist.

    API changes

    This adaptation includes no changes to API usage.

    iOS 16 adaptation

    After the official release in September 2022, you must adapt your app to the new system attributes and interfaces.

    • This baseline has completed the adaptation and testing for iOS 16 beta(8) for IPA packages built with Xcode 13.

    • If you plan to publish your application on the Apple App Store, use Xcode 13 for packaging.

    • The toolchain for Xcode 14 is under improvement. Once the toolchain is ready, mPaaS will release a version adapted for iOS 16 that is built with Xcode 14.

    The main adaptation points for iOS 16 involve updates to methods for screen orientation, clipboard usage, and image usage. The affected components include, but are not limited to, the following:

    • H5 container and offline package

    • Mini Program

    • Multimedia (Private Cloud)

    • Face verification (Private Cloud)

    • Mobile security keyboard (Private Cloud)

    • Base frame

    • Instrumentation and monitoring

    • Audio and video calls

    • Image recognition OCR (Private Cloud)

    • Code scanner

    • Map

    • Some internal dependent components

    Applications that use the components listed above must be thoroughly tested and verified on iOS 16 to ensure their features, compatibility, and stability.

    Handling custom baselines

    If you use a custom baseline, you may need to create a new custom baseline based on the new version. To confirm this, search for and join the DingTalk group (ID: 145930007362) and contact the mPaaS helpdesk.