Introduction

React/RCTBridgeModule.h file not found usually means Xcode cannot see the React Native iOS headers through the way the project is currently linked. In modern React Native projects, this is most often a CocoaPods integration issue, an incorrect import path in a native module, or opening the wrong Xcode project file. The fix is usually structural, not a random header-search-path hack.

What the Header Is For

RCTBridgeModule.h defines the protocol used to expose Objective-C or Swift-backed native modules to React Native JavaScript.

A typical Objective-C native module import looks like:

1#import <React/RCTBridgeModule.h>
2
3@interface MyModule : NSObject <RCTBridgeModule>
4@end

If Xcode cannot resolve that header, the iOS native build graph is not seeing the React Native pod headers correctly.

Start with the Most Common Cause: CocoaPods State

In most React Native iOS projects, the React headers come from CocoaPods. That means the first checks are:

• 'pod install completed successfully'
• you opened the .xcworkspace, not just the .xcodeproj
• Pods are not in a broken or stale state

A common repair sequence is:

cd ios
pod install

Then open:

• 'YourApp.xcworkspace'

not:

• 'YourApp.xcodeproj'

Opening the project without the workspace is one of the simplest ways to make pod-provided headers disappear.

Check the Import Style in the Native Module

For pod-based React Native setups, the usual import is:

#import <React/RCTBridgeModule.h>

Some older examples on the internet use different header layouts, and some library code includes compatibility guards such as __has_include. If you are maintaining a reusable native module, a conditional import can make the code more robust across project layouts.

1#if __has_include(<React/RCTBridgeModule.h>)
2#import <React/RCTBridgeModule.h>
3#else
4#import "RCTBridgeModule.h"
5#endif

That is more relevant for library authors than for a single application, but it explains why you may see different examples online.

Do Not Patch Header Search Paths Blindly

Many developers hit this error and immediately start editing Xcode header search paths manually. That sometimes masks the real issue and makes the project harder to maintain.

In a standard React Native app using CocoaPods, the better default is:

1. confirm the pods are installed
2. open the workspace
3. clean derived data if needed
4. rebuild

Manual search-path changes should be a last resort, not the first move.

Clean and Rebuild When Pod State Is Stale

If the pod installation is correct but Xcode still cannot resolve the header, clean build artifacts.

rm -rf ~/Library/Developer/Xcode/DerivedData
cd ios
pod install

Then rebuild from the workspace.

This often fixes stale indexing and cached build-state problems that survive normal recompiles.

Swift Native Modules Still Depend on Objective-C Bridging

Even if the module implementation is in Swift, React Native's bridge layer often still needs Objective-C compatibility glue or bridging headers. So a Swift-based native module can still surface the same RCTBridgeModule.h import issue.

That is why the error is not limited to Objective-C files.

Watch for use_frameworks! and Nonstandard Pod Configurations

If the Podfile uses use_frameworks! or other nonstandard settings, header exposure can behave differently than in the default static-library style many React Native guides assume. In those cases, the build can fail even when the import line itself is correct.

That does not mean use_frameworks! is impossible, but it does mean you should check whether the React Native version and the pod setup you are using are known to work together.

Common Pitfalls

A common mistake is opening the .xcodeproj instead of the .xcworkspace after installing pods.

Another mistake is copying an old import pattern from a different React Native version without checking how the current project structures headers.

People also often jump straight to manual header search path edits, which can hide a broken pod integration rather than fix it.

Finally, if the native module is reusable, remember that your app and your library may not share the same header layout assumptions.

Summary

• 'React/RCTBridgeModule.h file not found usually points to a React Native iOS integration problem, not a missing source file you should create manually'
• Start by running pod install and opening the .xcworkspace
• Use the normal React Native import path, and use conditional imports only when compatibility across layouts matters
• Clean derived data if pod state or Xcode indexing appears stale
• Be cautious with manual header search path edits because they often treat the symptom rather than the cause
• If the project uses nonstandard Podfile settings, verify that the React Native version and pod integration model are compatible