通过CocoaPods集成React Native到iOS旧项目：UIKit等框架构建失败

I’ve run into similar headaches when integrating React Native as a component Pod into legacy mixed-language projects, so let’s break down what’s likely going wrong and how to fix it:

1. Explicitly Declare System Frameworks in Your Podspec #

The example project probably implicitly pulls in system frameworks, but your legacy project’s CocoaPods setup might not. Open your React Native component’s podspec and make sure you explicitly list the required system frameworks:

s.frameworks = 'UIKit', 'CoreFoundation', 'Foundation'
# Add any other system frameworks your bridge code relies on

This tells CocoaPods to link these frameworks to your component Pod, ensuring the bridge header can resolve their imports.

2. Verify Bridging File Configuration #

• Check the bridging header path: In your Pod’s Xcode target, go to Build Settings > Swift Compiler - General > Objective-C Bridging Header. Make sure the path is relative to your Pod’s root directory (not the main project). For example, if your bridge file is at MyRNComponent/Bridge/MyRNBridge.h, set the path to MyRNComponent/Bridge/MyRNBridge.h.
• Enable module definition: Ensure Build Settings > Packaging > Defines Module is set to YES for your Pod target. This is critical for mixed-language Pods to work correctly with the main project.
• Use correct import syntax: In your bridge header, always use angle brackets for system frameworks:

  #import <UIKit/UIKit.h>
  #import <CoreFoundation/CoreFoundation.h>
  

  Avoid using quotes ("UIKit.h")—this tells the compiler to look in local directories instead of system framework paths.

3. Fix Build Settings Conflicts in the Main Project #

Legacy projects often have custom Header Search Paths or Framework Search Paths that can break Pod resolution. Add a post-install hook to your main project’s Podfile to standardize these paths for your RN component:

post_install do |installer|
  installer.pods_project.targets.each do |target|
    if target.name == 'YourRNComponentPodName'
      target.build_configurations.each do |config|
        # Add system framework search path
        config.build_settings['FRAMEWORK_SEARCH_PATHS'] = ['$(SDKROOT)/System/Library/Frameworks']
        # Ensure header paths include system headers
        config.build_settings['HEADER_SEARCH_PATHS'] = ['$(inherited)', '/usr/include']
      end
    end
  end
end

Run pod install again after updating the Podfile.

4. Clean and Rebuild to Clear Cache #

Legacy projects are prone to build cache issues. Follow these steps:

• Delete the Pods directory and Podfile.lock from your main project.
• Go to Xcode > Product > Clean Build Folder (hold Option to see this option).
• Delete Derived Data: Xcode > Settings > Locations > Derived Data > Click the arrow to open the folder, then delete its contents.
• Re-run pod install and build your project.

These steps should resolve the system framework import errors in your bridge header. Let me know if you hit any edge cases!

内容的提问来源于stack exchange，提问作者Vijay Tholpadi