When working with CocoaPods, it is sometimes necessary to remove the local Pod repo and re-sync. This is occasionally needed when new SDK releases become available and the client’s local CocoaPods repo needs to re-sync.
The following steps outline the removal of the First Orion Pod repository from the client and re-syncing.
$ pod repo-art remove fo-cocoapods-external
$ rm -rf ~/.cocoapods/repos/fo-cocoapods-external
$ pod cache clean --all
$ pod deintegrate
$ pod repo-art add fo-cocoapods-external "https://firstorion.jfrog.io/firstorion/api/pods/fo-cocoapods-external"
From the project’s main directory, pod install could also be used:
$ pod update
If a compiler error occurs while building the SDK in Xcode:
- Open the Pods project and select the ENGAGE target
- Verify that the Build Setting values for “Architectures” only includes the architectures supported by the enterprise app
- Set the “Build Active Architecture Only” build setting to “YES” for Debug only
- Try to build
Bitcode may be manually removed if it is not used. ENGAGE SDK should be manually added instead of Cocoapods. During this process, bitcode will need to be removed using Xcode runtime:
xcrun bitcode_strip -r Engage.xcframework/ios-arm64/Engage.framework/Engage -o EngageArm64NoBitcode
Updated 17 days ago