开启Enable Bitcode后arm64架构无法生成Bitcode bundle的技术求助

Hey Nick, I feel your pain—dealing with bitcode issues in a long-running mixed-language project can be such a headache, especially when you’ve already ruled out the usual suspects like pod dependencies. Let’s break down some less obvious checks and fixes that might get you past this linker error:

• Double-check all targets in your project
  Legacy projects often accumulate forgotten targets (like extensions, test bundles, or internal frameworks) that might not have their Enable Bitcode setting synced to YES. Go to your project’s settings, switch to the "Targets" tab, and verify every single target (including any nested ones) has this option enabled. Even a single overlooked target can trigger this linker error.

• Verify build configuration consistency for Debug mode
  Your error occurs during a Debug-iphoneos build. By default, Xcode uses -fembed-bitcode-marker for Debug builds (a lightweight placeholder) and -fembed-bitcode for Release/Archive. But custom build flags can sometimes override this:

  • Check Build Settings > Other C Flags and Other Swift Flags for your Debug configuration—make sure there’s no -fno-bitcode flag present that’s disabling bitcode generation.
  • Confirm Enable Bitcode is set to YES specifically for the Debug configuration (not just Release). It’s easy to accidentally set it only for one build type.

• Inspect Swift compiler settings for mixed-language code
  Since your project combines Objective-C and Swift, ensure the Swift compiler’s bitcode setting is aligned. Go to Build Settings > Swift Compiler - Code Generation > Enable Bitcode and confirm it’s set to YES for all relevant configurations. Sometimes this setting doesn’t inherit from the main target’s general Enable Bitcode toggle, especially in older Xcode versions like 9.2.

• Do a full Cocoapods reset (beyond just deleting Derived Data)
  Deleting Derived Data clears local build artifacts, but Cocoapods might have cached old builds of your dependencies without bitcode. Try these steps:

  1. Run pod deintegrate in your project directory to fully remove all pod integrations.
  2. Delete the Pods/ folder and Podfile.lock.
  3. Run pod install to rebuild all dependencies with your current bitcode settings.

• Check the actual compile command for main.o
  The error points directly to main.o lacking full bitcode. Let’s verify how this file is being compiled:

  1. In Xcode, find your main.m (or main.swift) file in the project navigator.
  2. Right-click it and select Show in Build Log.
  3. Look for the compile command line—ensure it includes either -fembed-bitcode-marker (Debug) or -fembed-bitcode (Release). If this flag is missing, something in your build settings is suppressing it.

• Test with an Archive build instead of Debug
  The error message mentions that bitcode requires files generated from an Archive or Install build. Debug builds use the marker which is sometimes not sufficient for full bitcode validation. Try creating an Archive of your project (Product > Archive) and see if it succeeds. If it does, the issue might be isolated to Debug mode, and you can adjust your Debug build settings to use -fembed-bitcode temporarily for testing (note this will slow down Debug builds).

• Check for legacy build flags or incompatible settings
  Since your project dates back to 2012, there might be outdated build flags that conflict with bitcode. Look for settings like:

  • Compile Sources As (ensure it’s set correctly for your files, not forcing an incompatible mode)
  • Other Linker Flags—remove any deprecated flags that might interfere with bitcode linking.

If none of these work, try comparing your legacy project’s build settings side-by-side with the newer projects where bitcode works. Subtle differences in flags, SDK versions, or target configurations could be the culprit.

内容的提问来源于stack exchange，提问作者Nick Daly