Mobile Platform as a Service:How to resolve OpenSSL third-party library conflicts in an iOS project

When you integrate mPaaS, the mPaaS custom OpenSSL library may conflict with other third-party OpenSSL libraries in your project. To resolve this conflict, remove the conflicting library from your project and use the custom library provided by mPaaS. If API incompatibilities occur because your project uses a newer version of OpenSSL, you must import a newer custom OpenSSL library. You can import a newer custom OpenSSL library in one of the following two ways:

• Using the mPaaS Xcode Extension

• Using the CocoaPods plugin

Using the mPaaS Xcode Extension

This method is for projects that already use the mPaaS Xcode Extension to manage the mPaaS framework.

1. In the extension, click the Edit Project button. Use the Upgrade Baseline feature, select Custom Baseline, enter the baseline ID cp_change_20300, and click Confirm to complete the upgrade.

   Note

   This custom baseline aligns with the standard baseline 10.1.68.34.

2. After the baseline is upgraded, select Edit Module from the top menu. Then, select the OpenSSL Module and add it to your project to import the custom library and resolve the conflict.

Using the CocoaPods plugin

This method is for projects that already use the CocoaPods plugin to manage the mPaaS framework.

1. In the terminal, navigate to the directory that contains your project's Podfile. Run the pod mpaas update cp_change_20300 command to update the baseline.

   Note

   This custom baseline aligns with the standard baseline 10.1.68.34.

2. Change the baseline version in your Podfile to cp_change_20300 and add the code mPaaS_pod "mPaaS_OpenSSL". Then, run pod install in the terminal to import the custom OpenSSL library and resolve the conflict.