Reputation: 4815
I'm using Xcode 9.0.
My pod file:
pod 'Alamofire', '~> 4.3'
pod 'SwiftyJSON'
pod 'AlamofireSwiftyJSON'
pod 'KSToastView', '0.5.7'
pod 'SDWebImage', '~> 4.0'
pod 'NVActivityIndicatorView'
pod 'Firebase/Core'
pod 'Firebase/Messaging'
pod 'CarbonKit'
pod 'SBPickerSelector'
pod 'SwiftyStoreKit'
pod 'Fabric'
pod 'Crashlytics'
pod 'SAMKeychain', '1.5.2'
My error log:
ld: could not reparse object file in bitcode bundle: 'Invalid bitcode version (Producer: '902.0.39.2_0' Reader: '900.0.37_0')', using libLTO version 'LLVM version 9.0.0, (clang-900.0.37)' for architecture arm64 clang: error: linker command failed with exit code 1 (use -v to see invocation)
I read many articles for this issue but I'm not able to solve it. I referred to this, and yes, this takes note that I want to build archive my project with
configuration = Debug
ENABLE_BITCODE = YES
configuration = Release
ENABLE_BITCODE = YES
completeSettings = some
ENABLE_BITCODE = YES
Any suggestions?
Upvotes: 30
Views: 28998
Reputation: 878
Work for me set the option
ENABLE_BITCODE=no
will successfully run the build but this is NOT a good workaround.
(You have to go to the in xcode to the project>build settings, and select the "All" filter, then search by ENABLE_BITCODE key and change it)
Upvotes: 0
Reputation: 3914
To anyone experiencing this still, you might have packages/pods built with a higher version of Xcode than you installed. I've resolved it by upgrading my XCode to the latest.
I don't think turning off the Bitcode option is the right way to go about it. It's a symptom, not the solution.
Upvotes: 0
Reputation: 531
This is because you have some dependencies in your project (frameworks) that is built with a newer version of Xcode.
You have to update your Xcode version, or disable bit code in your project (Project > Build Settings > Enable Bitcode = NO)
Upvotes: 20
Reputation: 5939
There is a big chance that the Xcode version that compiled the pod sdk is higher than the one you are using.
Next possible reason is the bitcode in build settings. Check if it is enabled on your app target and your framework target. If you have added vis cocoapods, click on pods project, under targets section, scroll down to the sdk which is giving this error, open the build settings and check for the bitcode status.
In my case, the Main project had bitcode disabled and the sdk inside the pods project had it enabled. Disabled it and everything worked fine.
Upvotes: 0
Reputation: 231
This could also happen if you have two different Xcode versions installed side by side and then building with one that points to wrong command line tools. I experienced this problem after installing Xcode 10.1 next to (updated) Xcode 10.2. My Xcode 10.1 was pointing to Xcode 10.2 command line tools, so linking failed with invalid bitcode version, same as in your case. The fix was:
Change Command Line Tools in Xcode Preferences -> Locations -> Command Line Tools:
Clean build folder and hit Archive.
The above is also valid for other Xcode versions.
Upvotes: 18
Reputation: 532
Steps to solve this issue:
Upvotes: 46
Reputation: 861
As Rivera said, some libraries you use expect Xcode 10 (probably Firebase). So the workaround is to downgrade versions of your libraries. For me those versions works well with Xcode 9 and bitcode enabled option:
pod 'Firebase/Core', '~> 4.13.0'
pod 'Fabric', '~> 1.7.0'
pod 'Crashlytics', '~> 3.9.0'
Probably you should also investigate which old version of Firebase/Messaging to use.
BTW, that is one of the reasons why developers should avoid using pods without specifying the specific version (which will lead to always download the latest versions of pods). It also may lead to version incompotability with your code which is using pod features.
Upvotes: 5
Reputation: 10938
Some libraries you use expect Xcode 10 (probably Firebase). Use Xcode 10.
Upvotes: 1