iOS 16 introduces changes to screen orientation, clipboard usage, and image handling that can break apps built on earlier mPaaS baselines. mPaaS baseline 10.1.68 addresses these changes. This topic describes what changed and the steps required to upgrade and configure your app.
The adaptation involves three steps:
Upgrade to baseline 10.1.68 (or confirm you are already on it).
Configure JSAPI security for H5 containers and Mini Programs.
Test all affected components on a device running iOS 16.
Prerequisites
Before you begin, make sure you have:
Xcode 13: Use Xcode 13 to build and package your app. Xcode 14 is not yet supported — do not use it for App Store submissions until mPaaS releases a Xcode 14-compatible version.
Baseline 10.1.68.53 or later: mPaaS has completed iOS 16 adaptation and testing for baseline 10.1.68.53 and later. IPA packages must be built with Xcode 13.
Upgrade the baseline
Choose an upgrade path based on how you currently manage dependencies. The Extension plugin supports two upgrade methods:
|
Your current setup |
Action |
|
Extension plugin; baseline earlier than 10.1.68 |
Use Upgrade baseline in the plugin to move to 10.1.68. |
|
Extension plugin; already on baseline 10.1.68 |
Use Update product set in the plugin to update the modules you use. |
|
No Extension plugin (manual dependency management) |
Follow the steps in the Upgrade without the Extension plugin section below. |
|
CocoaPods |
Follow the steps in the Upgrade using CocoaPods section below. |
|
Custom baseline other than 10.1.68 |
Contact your helpdesk or technical support for guidance on which baseline to use. |
To check your current baseline version, open the Extension plugin and go to Baseline Upgrade.
Upgrade without the Extension plugin
If you do not use the Extension plugin to manage component dependencies, follow these steps:
Use the Edit Module feature to select the 10.1.68 baseline and add the required modules.
Upgrade using CocoaPods
In your Podfile, set the mPaaS component version to 10.1.68.
-
Run
pod mpaas update 10.1.68.If a command error occurs, run
pod mpaas update --allto update the plugin first, then run the command again. Run
pod install --repo-update.
Custom baselines
Contact your helpdesk or technical support for information about which baseline to use.
Security configuration
Apps built on the mPaaS framework that use H5 containers or Mini Programs typically rely on JavaScript APIs (JSAPIs). Without proper URL validation, external pages can misuse app information, bypass authentication, or invoke JSAPIs with unintended scope.
Configure the following before publishing:
Set JSAPI authentication — restricts which URLs can invoke JSAPIs and with what permissions.
Set a URL whitelist — ensures that only URLs related to your app's services are loaded.
API changes
This adaptation includes no API changes. No code changes are required.
iOS 16 adaptation
The following components have been adapted and tested for iOS 16 beta(8) with IPA packages built on Xcode 13:
|
Component |
Status |
| H5 container and offline package | Adapted and tested |
| Mini Program | Adapted and tested |
| Multimedia (Private Cloud) | Adapted and tested |
| Face verification (Private Cloud) | Adapted and tested |
| Mobile security keyboard (Private Cloud) | Adapted and tested |
| Base frame | Adapted and tested |
| Instrumentation and monitoring | Adapted and tested |
| Audio and video calls | Adapted and tested |
| Image recognition OCR (Private Cloud) | Adapted and tested |
| Code scanner | Adapted and tested |
| Map | Adapted and tested |
| Some internal dependent components | Adapted and tested |
Thoroughly test each component your app uses on a device running iOS 16 before submitting to the App Store.
Handling custom baselines
If you use a custom baseline, you may need to create a new custom baseline based on the updated version. To confirm, search for and join the DingTalk group (ID: 145930007362) and contact the mPaaS helpdesk.