Linker errors when building with Xcode 12 and CocoaPods — building for iOS Simulator, but linking in dylib built for iOS #2665
Comments
1ec5
added
build
|
Tracking the minimum deployment target warnings above in #2666. |
|
Locally, I tried adding both these lines to the test podspec: s.user_target_xcconfig = { 'EXCLUDED_ARCHS[sdk=iphonesimulator*]' => 'arm64' }
s.pod_target_xcconfig = { 'EXCLUDED_ARCHS[sdk=iphonesimulator*]' => 'arm64' }and it linted and pushed successfully: CocoaPods/Specs@fdd6fa9. The CocoaPods maintainers are against modifying |
|
@1ec5 with the workaround successfully in place, does this mean that this is no longer a release blocker (but still worth keeping open)? |
I’ve only applied the workaround to a throwaway podspec that’s based on the ones in this repository, to prove that it’ll work. The next step is to apply it to the podspecs in this repository. The release is still blocked on making that change. The more correct fix in MapboxAccounts – rebuilding it to include an arm64 simulator slice – will have to wait until after the v1.0.0 release. Once that more correct fix is in place, we can remove the workaround from this repository. That’ll be highly desirable – in general, we don’t want to toy with the application target’s build settings – but will have to wait until v1.0.1. |
#2672 tracks removing the workaround when it’s safe to do so. |
Xcode 12 raises linker errors about architectures when building the navigation SDK using CocoaPods. These warnings also cause CocoaPods to reject any attempt to push the MapboxCoreNavigation or MapboxNavigation pod to CocoaPods trunk.
Problem details
To validate the fix in #2662 for the CocoaPods linter error in #2646 (comment), I tried pushing to a throwaway pod on CocoaPods trunk and ran into errors doing so with the combination of CocoaPods 1.10.0.rc.1 and Xcode 12:
The verbose output contains additional details about the linker errors:
Workarounds
As a temporary workaround, I
xcode-selected Xcode 11.7 and tried again, this time successfully: CocoaPods/Specs@23ef623.However, this workaround only makes it possible to push the pod to CocoaPods trunk; application developers using Xcode 12 are still affected by the linker errors. A more robust workaround requires modifying the podspecs to exclude Apple Silicon from the valid architectures: CocoaPods/CocoaPods#10065 (comment) CocoaPods/CocoaPods#10104 (comment).
Solution
A more long-term solution will require rebuilding MapboxAccounts with all the architectures required by Xcode 12. In the meantime, we should apply the workaround in CocoaPods/CocoaPods#10065 (comment) CocoaPods/CocoaPods#10104 (comment) to the podspecs in this repository.
/cc @mapbox/navigation-ios @mapbox/core-sdk
The text was updated successfully, but these errors were encountered: