59

Recently i downloaded xcode 7 beta and facing the error:

-fembed-bitcode is not supported on versions of iOS prior to 6.0

Is there any work around to fix this issue with out changing deployment target?

Thanks in advance.

user102008
  • 30,736
  • 10
  • 83
  • 104
Kiran
  • 1,145
  • 1
  • 8
  • 22
  • I would suggest you consider removing support for iOS 5. Most of the libraries are going to be built with bitcode now. Disabling bitcode would mean that you can't support Watch OS – Gautam Jain Sep 15 '15 at 09:54
  • @Gautam: Watch OS need separate libs that are build for Watch OS anyways. That means a separate build target, so no need to keep bitcode enabled in the iOS target just for Watch OS. However there are of course other reasons to keep it enabled when building for iOS. – Kaiserludi Oct 28 '15 at 10:35

2 Answers2

115

Found this recently, which seems to imply that you need to enable bitcode for each framework.

"Xcode 7 has a ENABLE_BITCODE option to embed bitcode in apps, app extensions, and frameworks. The option is turned on by default for iOS and is mandatory for watchOS projects submitted to the store. When bitcode is enabled for a target, all the objects, static libraries and user frameworks used when linking that target must contain bitcode. Otherwise, an error or a warning will be issued by the linker. (Note: missing bitcode is currently a warning for iOS, but it will become an error in an upcoming beta release of Xcode 7.) ENABLE_BITCODE should be consistently turned on for all the targets. If you use a library or framework provided by a third party, please contact the vendor for an updated version which contains bitcode." Dear God, do we need to wait for all libs to update? :S

Source (link)

If you don't plan to support Apple Watch you can turn off the option by searching for BITCODE in the project and the target. Change the option to No.

bitcode

Tommie C.
  • 12,895
  • 5
  • 82
  • 100
2

I was trying to run the AudioModem code (set to target iOS 5.1) on an iOS 9.1 device. For me, simply changing the deployment target of the app to 9.0 (incredibly!) worked (somehow without introducing other errors?!).

Michael
  • 2,973
  • 1
  • 27
  • 67