Mobile Platform as a Service：How to solve the OpenSSL conflict in iOS projects

When integrating to mPaaS, the OpenSSL custom library provided by mPaaS may conflict with the OpenSSL third-party library introduced in the project. In this case, you can remove the OpenSSL library introduced in the project and use the OpenSSL custom library provided by mPaaS for adaptation. If after adaptation, if the interface is incompatible due to a higher version of the OpenSSL library used in the previous project, you need to introduce a higher version of the OpenSSL custom library separately. You can introduce a higher version of the OpenSSL custom library in the following two ways:

• Based on mPaaS Xcode Extension plugin

• Based on CocoaPods plugin

Based on mPaaS Xcode Extension plugin

This method is suitable for projects that have adopted the mPaaS Xcode Extension plugin to manage the mPaaS framework.

1. In Extension plugin, Click the Edit Project button to open the project, use the Upgrade Baseline function, select Custom Baseline, enter the Baseline ID: cp_change_20300, and click Confirm to upgrade.

   Note

   The standard baseline that this custom baseline feature is aligned to is 10.1.68.34.

2. After upgrading the baseline, select Edit Module in the upper menu, select OpenSSL module and add it to the project to introduce the custom library to resolve the conflict.

Based on CocoaPods plugin

This approach is suitable for projects that have adopted the CocoaPods plugin to manage the mPaaS framework.

1. Type the command in the terminal to enter the same level directory of the project Podfile, and execute the command of pod mpaas update cp_change_20300 to update the baseline.

   Note

   The standard baseline functionally equivalent to the custom baseline is 10.1.68.34.

2. Change the Podfile baseline version to cp_change_20300 and add the code: mPaaS_pod "mPaaS_OpenSSL", then execute the command of pod install in the terminal to successfully introduce the custom OpenSSL library to resolve the conflict.