React Native iOS .ipa打包失败：编译及链接错误排查求助

Let's break down the two issues you're facing and walk through actionable fixes step by step.

1. Initial react-native-ffmpeg CompileC Error #

The first failure in RNExecuteDelegate.m usually stems from dependency mismatches, stale build caches, or architecture conflicts. Here's how to resolve it:

• Clean stale DerivedData (this is a common fix for weird Xcode build glitches):
  Run this terminal command to wipe all of Xcode's cached build files:

  rm -rf ~/Library/Developer/Xcode/DerivedData
  

• Verify react-native-ffmpeg compatibility:
  Double-check that your react-native-ffmpeg version matches your React Native version. For example, if you're on RN 0.68+, use the latest stable release of the library (refer to the package's README for official compatibility notes).
• Reinstall CocoaPods:
  Navigate to your project's ios directory and run:

  pod deintegrate && pod install
  

  This ensures all pod dependencies are properly linked and updated to their correct versions.
• Tweak Xcode architecture settings:
  Open your project's .xcworkspace in Xcode, go to your target's Build Settings:
  • Set Architectures to Standard Architectures (arm64, x86_64)
  • Add arm64 to Excluded Architectures for the Release-iphonesimulator configuration (this resolves conflicts between simulator and device architectures)

2. Subsequent Ld arm64 Linker Error #

After fixing the ffmpeg issue, the linker error for arm64 typically happens due to leftover cache, incorrect architecture settings, or missing library links. Try these steps:

• Re-clean DerivedData and build folder:
  Besides wiping DerivedData, also clean your Xcode build folder directly:
  In Xcode, press Cmd+Shift+K to clean the build folder, then run rm -rf ~/Library/Developer/Xcode/DerivedData again to eliminate all residual cache.
• Validate Xcode linker settings:
  Go to your target's Build Settings:
  • Ensure Valid Architectures includes arm64
  • Check Other Linker Flags for duplicate or invalid entries (remove any unnecessary -l or -framework flags that might be causing conflicts)
• Build directly from Xcode for clearer error details:
  Instead of using the CLI command, open your .xcworkspace in Xcode, select the Release configuration, and run Product > Archive. This will show you a more detailed error log if the linker fails, helping you pinpoint exactly which symbol or library is missing.
• Adjust Apple Silicon compatibility settings:
  If you're using an Apple Silicon Mac:
  • Set Build Active Architecture Only to Yes for Debug and No for Release in your target's Build Settings
  • Ensure Rosetta 2 is installed if you're using older pods that still require it

Why DerivedData Is Often the Culprit #

Xcode stores temporary build files, intermediate binaries, and cached data in DerivedData. When you update dependencies, change configuration settings, or switch between build types (Debug/Release), these cached files can become outdated or corrupted, leading to unexpected compile/link errors. Wiping DerivedData forces Xcode to rebuild everything from scratch, which resolves most cache-related issues.

内容的提问来源于stack exchange，提问作者Anayo Samson Oleru