Fix: all bitcode will be dropped in Xcode

Fix: all bitcode will be dropped in Xcode

Written by

in

Quick answer: In an older Xcode project, fix the all bitcode will be dropped warning by setting Enable Bitcode (ENABLE_BITCODE) to No for the affected target and build configuration. The warning means a linked library lacks the bitcode requested by your build settings. Bitcode is obsolete in current Xcode toolchains, so do not enable it to satisfy modern App Store submission requirements.

Why this happens

The warning all bitcode will be dropped comes from an older build workflow in which your target requests embedded bitcode, but a linked library does not provide it. The source example involves Parse.framework, with PFAnalytics.o identified as an object file built without bitcode. The same mismatch can occur with other precompiled dependencies.

Bitcode is an LLVM intermediate representation of compiled code. Historically, supported Xcode toolchains could embed it alongside native machine code in an app binary for Apple’s distribution processing. Enabling bitcode did not replace the executable with an intermediate file that could not run: a normal device build still contained executable machine code.

The modern context matters. Apple deprecated bitcode with Xcode 14, and Xcode 15 removed support for it. Advice suggesting that bitcode might eventually become mandatory is outdated. For a current project, the goal is to remove legacy bitcode requirements, not introduce them.

How to fix it

1. Disable bitcode on the affected target in an older Xcode project

If you are maintaining a project with an older Xcode version that exposes this setting, disable bitcode where the warning originates:

  1. Select the project in Xcode’s Project navigator.
  2. Under TARGETS, select the target producing the warning.
  3. Open Build Settings.
  4. Select All, rather than Basic, so Xcode shows the full set of available settings.
  5. Search for Enable Bitcode or ENABLE_BITCODE.
  6. Set the value to No for the relevant configurations, including the configuration used for archiving.
  7. Build again and check the build log.

Selecting All is important: the setting can be absent from the filtered view even when the older toolchain supports it.

For a project managed through configuration files, the equivalent setting is:

ENABLE_BITCODE = NO

Add this to the appropriate .xcconfig file only if your project uses configuration files. Check for a target-level override, because changing a shared configuration does not help if the target explicitly sets a different value.

This is the practical fix for an older iOS app whose dependency does not contain bitcode. It removes the request that caused the mismatch; it does not repair or rebuild the dependency itself.

2. Check the archive configuration, not just Debug

A successful Debug build does not prove that an archive uses the same settings. Projects commonly have separate Debug and Release values, and some use a custom configuration for distribution.

Open Product > Scheme > Edit Scheme, select the Archive action, and inspect its build configuration. Then check ENABLE_BITCODE for that configuration on the target named in the warning.

Also inspect any separately built targets involved in the failure, such as an app extension or an internal framework. Changing the app target does not automatically change every target in the project.

For a command-line view of the resolved build settings, use a command such as:

xcodebuild \
  -project MyApp.xcodeproj \
  -scheme MyApp \
  -configuration Release \
  -showBuildSettings | grep ENABLE_BITCODE

Replace the project, scheme, and configuration with your own values. If you build a workspace, use -workspace MyApp.xcworkspace instead of -project MyApp.xcodeproj.

This check helps distinguish the value you edited from the value the build actually receives. In a modern toolchain, the setting may be absent or remain only as a legacy project entry; its presence does not mean that toolchain supports generating bitcode.

3. Update or rebuild the library only when an older workflow requires bitcode

The other historical solution is to replace the dependency with a build that includes bitcode, or rebuild it from source using a compatible older toolchain and appropriate settings.

That approach makes sense only when you must preserve a legacy workflow that genuinely requires bitcode. The requirements were not identical across all Apple platforms and historical toolchains, so do not apply old iOS advice indiscriminately to an archived watchOS or tvOS project.

For a precompiled framework, changing the consuming app’s settings cannot insert missing bitcode into the framework. You need either:

  • A compatible framework supplied by its maintainer.
  • A source build produced with the required settings.
  • A build configuration that no longer requires bitcode.

For current development, prefer a maintained dependency compatible with your current Xcode version. Do not downgrade Xcode solely to recreate bitcode support.

4. Remove legacy bitcode configuration from modern builds

If the project now builds with a current Xcode toolchain, review old configuration rather than searching indefinitely for an Enable Bitcode switch.

Look through project settings, .xcconfig files, and build scripts for explicit bitcode requirements. In particular, check custom compiler options such as -fembed-bitcode and -fembed-bitcode-marker. Remove legacy options that your project no longer needs, while preserving unrelated compiler and linker flags.

If the warning persists, inspect the full build log to identify which command emits it. A script might invoke a separately selected toolchain or build an old dependency independently of the main app target. Fix that build step rather than repeatedly changing the app’s settings.

After updating the configuration, build and archive again. Clearing build products is not a substitute for resolving a configuration mismatch.

5. Verify submission and performance separately

Disabling bitcode is not, by itself, a barrier to modern App Store submission. Current Xcode workflows do not require it. Archive the app and use Xcode’s distribution validation to check the actual submission requirements; unrelated signing, SDK, or packaging errors still need their own fixes.

There is also no universal runtime performance penalty from setting ENABLE_BITCODE to NO. The app runs native machine code, not embedded bitcode. Compiler optimization settings, application code, and dependency implementations are more useful places to investigate a performance problem.

Do not assume that disabling bitcode makes installed apps larger, either. Embedded bitcode could increase archive size, while App Store app thinning is a separate distribution mechanism. Comparing archive sizes alone does not establish a change in installed size or runtime speed.

How to prevent it

  • Keep dependencies compatible with the Xcode version used locally and in continuous integration.
  • Review inherited build settings when migrating an older project.
  • Check the archive configuration before treating a Debug build as proof that distribution works.
  • Avoid copying obsolete bitcode flags into new targets or build scripts.
  • Treat warnings about individual framework object files as dependency-compatibility clues, not necessarily defects in your Swift code.

FAQ

Is Enable Bitcode required for App Store submission?

Not for modern Xcode submissions. Bitcode was deprecated in Xcode 14, and support was removed in Xcode 15. Historical platform requirements should not be used as instructions for a current app.

Why can’t I find Enable Bitcode in Build Settings?

In an older Xcode version, switch the Build Settings filter from Basic to All and search for ENABLE_BITCODE. In a modern Xcode version, bitcode support has been removed, so a missing setting is not something you need to repair.

Will turning bitcode off slow down my app?

There is no general slowdown caused simply by disabling embedded bitcode. Measure performance with an appropriately optimized build on a real device, and investigate the generated app’s behavior rather than treating this legacy distribution setting as a speed switch.

Sources & credits

Parts of this guide are adapted from content licensed under CC BY-SA 3.0; this article is shared under the same license.