Invalid bitcode signature on xcode

xcode bitcode
Oded Harth picture Oded Harth · Apr 11, 2017 · Viewed 47.7k times · Source

After updating Xcode to version 8.3 I'm getting this error:

error: Invalid bitcode signature
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Bitcode is not even enabled on my project.

How can I fix this?

Answer

Jack picture Jack · Apr 11, 2017

Try some tricks ->

  • Clear derived data & reopen xcode.

  • Select proper sign in / certificate, or try to re add account in xcode

  • Make sure if your pods supported bitcode if not then you need to set bitcode to NO (Go to Project Build setting search for bitcode & set it to NO.

Hope it will helpful:)

Related questions

New warnings in iOS 9: "all bitcode will be dropped"

I have this new warning about the Google Framework in my app: (null): URGENT: all bitcode will be dropped because '/Users/myname/Library/Mobile Documents/com~apple~CloudDocs/foldername/appname/GoogleMobileAds.framework/GoogleMobileAds(GADSlot+AdEvents.o)' was built …

Read More
Impact of Xcode build options "Enable bitcode" Yes/No

Yesterday I recognized a ton of warnings regarding the parse.com library: URGENT: all bitcode will be dropped because '[path]/Parse.framework/Parse(PFAnalytics.o)' was built without bitcode. You must rebuild it with bitcode enabled (Xcode setting …

Read More
How do I xcodebuild a static library with Bitcode enabled?

Xcode 7 introduces Bitcode, which is some sort of LLVM intermediate binary that means Apple's servers can recompile my app for different architectures without my involvement. At Lookback, I distribute a static archive framework with our library. It seems that when …

Read More