Use mPaaS 10.2.3 and adapt to iOS 16

Baseline description

This baseline is built on the latest mPaaS 10.1.68.53 product set. It integrates modifications from previous custom baselines, new components, and compliance enhancements. Features include but are not limited to the following:

Security and compliance

Security Guard SDK provides enhanced security capabilities and supports digital signatures that use Chinese national cryptography.

New components

• mPaaS GMSSL (private cloud)

• Mobile Dispatch Center (MDC)

• Application Performance Management (APM)

• Face verification (private cloud)

• Mobile terminal environment detection (private cloud)

• Mobile Threat Awareness Platform or device risk consulting (private cloud)

• Intelligent Dual-Recording System

Updated components

• OpenSSL is fully upgraded to resolve conflicts with other open source libraries.

• AlipaySDK is upgraded for compatibility. If you encounter conflicts or functional issues, see Notes on Integrating the Alipay Open Platform Express Payment SDK.

Upgrade the baseline

Choose an upgrade method based on your current baseline version.

Current baseline is the 10.1.68 main baseline

Upgradation based on the Extension plug-in

• If you use the mPaaS extension to manage component dependencies and your current baseline version is earlier than 10.2.3, use the Upgrade Baseline feature to upgrade to version 10.2.3.

  Note

  You can view the current baseline version in the Upgrade Baseline section of the extension.

• If you already use the extension to manage component dependencies and your current baseline is 10.2.3, use the Update Product Set feature to upgrade the modules you use.

• If you do not use the extension to manage component dependencies, upgrade as follows:

1. Install the mPaaS Xcode Extension.

2. Use the Edit Module feature to select the 10.2.3 baseline and add the required modules.

Upgrade using CocoaPods

Follow these steps to install the latest SDK for version 10.2.3:

1. First, ensure that the version number for mPaaS components in your Podfile is 10.2.3.

2. Run pod mpaas update 10.2.3.

   If the command fails, first update the plugin by running pod mpaas update --all, and then run the command again.

3. Run pod install --repo-update.

Current baseline is a custom baseline other than 10.1.68

Join the DingTalk group (ID: 145930007362) and ask the after-sales team or technical support staff if you can switch to the 10.2.3 baseline.

Update the configuration

Configure the V6 Security Guard image

The 10.2.3 baseline upgrades Security Guard SDK to support SM-series algorithm signatures. After the upgrade, you must replace the Security Guard image with the V6 version, because the 10.1.68 baseline uses V5 by default. Generate a V6 image and replace the existing `yw_1222.jpg` image in your project by following the steps below.

Important

You must follow these steps to configure the Security Guard image for both public cloud and Apsara Stack.

1. Install the mPaaS command line interface. The command line interface is included with the plugin. You can skip Xcode signing by answering 'N' when prompted during installation.

2. Generate a new Security Guard image. For more information, see Basic tool commands. The following is an example.

   Important

   • Replace the config file path, object file path, and appsecret with your actual values.

   • You can obtain the appsecret from the Code Management > Code Configuration > iOS tab in the mPaaS console.

   mpaas inst sgimage -c /path/to/Ant-mpaas-0D4F511111111-default-IOS.config -V 6 -t 1 -o /path/to/output --app-secret sssssdderrff --verbose

If you need Security Guard to support SM-series algorithms, see Configure gateway data signing for instructions.

Hotpatching update

If you have integrated the hotpatching feature into your project, contact the after-sales team or technical support staff to upgrade the hotpatching SDK.

Security configuration

Applications built on the mPaaS framework that use H5 containers or mini programs often call JSAPIs. To prevent external pages from misusing application data, validate URLs when they are opened or when JSAPIs are invoked. This ensures that only internal business URLs can be loaded. You can also restrict the scope and permissions of JSAPI calls for a URL to prevent unauthorized access.

For specific authentication methods, see the following documents:

1. Set JSAPI authentication.

2. Set a URL whitelist.

API changes

There are no API usage changes in this version.

Adapting to iOS 16

iOS 16 is scheduled for official release in September 2022. Applications need to be adapted for the new system features and interfaces.

• This baseline has been adapted for and tested on iOS 16 beta 8 by building an IPA package with Xcode 13.

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

• The toolchain for Xcode 14 is still under development. After the toolchain is complete, mPaaS will release a version that is adapted for iOS 16 and built with Xcode 14.

The main iOS 16 adaptations involve interface orientation methods, clipboard usage, and image handling. The affected components include:

• H5 container and offline package

• Mini Program

• Multimedia

• Face verification

• Mobile Security Keyboard (MSK)

• Basic framework

• Event tracking monitoring

• Mobile Real-Time Communication (MRTC)

• Optical Character Recognition (OCR)

• Scan

• Map

• Some internal dependent components

If your application uses any of the components listed above, fully test and verify it on iOS 16 to ensure functionality, compatibility, and stability.