`React/RCTBridgeModule.h` file not found

Question

Getting this error while building a react-native iOS app on xcode.

Started getting this error after npm install and rpm linking react-native-fs library. But after searching online for a solution, I noticed that many people are getting the same error while installing other react native libraries.

A possible solution suggested by many is, Adding the following under "Build Settings" -> "Header Search Paths".

$(SRCROOT)/../node_modules/react-native/React - (Recursive)

But no luck with this solution, still getting the same error

I'm getting this same error with v0.41.2, it should work with but it doesn't :/ — pgarciacamou, Feb 17 '17 at 22:18
@CecilRodriguez What version do you have for react-native-fs?. If you are manually adding with XCode please check https://github.com/itinance/react-native-fs#adding-manually-in-xcode — Shubham Khatri, Apr 27 '20 at 18:15
I am getting this error :Unable to resolve module `react-native-webrtc` — Ankita, Jun 16 '20 at 09:55
If you've having M1 chip then this should fix it. https://stackoverflow.com/a/68275769/2643815 — Smart Coder, Aug 15 '21 at 22:48
I our case we've get same error in two Macs with M1 cpu, and the solution to run the App was through Xcode going to Product, Destination, Destination Architecture and choose Show Rosetta destination. After that, the error stay but the App start running in emulator. — Sebastian Diaz, Jul 26 '23 at 19:23

score 169 · Accepted Answer · edited Aug 19 '19 at 14:52

169

In my case this particular problem happened when I was trying to archive a 0.40+ react-native app for iOS (solution was found here: Reliable build on ^0.39.2 fails when upgrading to ^0.40.0).

What happened was that Xcode was trying to build the react-native libraries in parallel and was building libraries with implicit react dependencies before actually building the react library.

The solution in my case was to:

Disable the parallel builds:
- Xcode menu -> Product -> Scheme -> Manage Shemes...
- Double click on your application
- Build tab -> uncheck Parallelize Build
Add react as a project dependecy
- Xcode Project Navigator -> drag React.xcodeproj from Libraries to root tree
- Build Phases Tab -> Target Dependencies -> + -> add React

edited Aug 19 '19 at 14:52

Edgar

6,022
8
33
66

answered Apr 11 '17 at 08:38

agiaLab

1,855
1
12
6

1

I have discovered that this only happens when you're upgrading to react-native 0.40+ from below. Project that are initilized with the 0.40+ RN already have parallel builds turned off. – agiaLab Apr 18 '17 at 13:14
33

What does "drag to root tree" mean? And the "Build Phases Tab" ... is this the Build Phases of React.xcodeproj? – GreenAsJade Jun 26 '17 at 12:02
4

When this bug appears after creation of a new target, step 1 is enough :) – Kepedizer Apr 23 '18 at 19:44
When adding React as a target dependency, make sure to add it ABOVE your app as described in this answer: https://stackoverflow.com/a/52425997/4744177 – Eugene Kim Oct 30 '18 at 05:59
3

How do you deal with an Expo ejected project? I don't have React.xcodeproj anywhere, React is in Podfile dependencies – Sebastien Lorber Dec 13 '18 at 11:11
1

@SebastienLorber open node_modules and drag react project from there – Ramon Canales Dec 17 '18 at 22:44
For expo, copy the the file from `PROJECT_ROOT/node_modules/react-native/React/React.xcodeproj` @SebastienLorber – Elijah Murray May 28 '19 at 03:31
Why should I disable parallel builds to fix this issue, I've to use that feature to reduce the build time. any other solution? – utkarsh-devops Jul 30 '19 at 09:05
This fixed it for me, but here is the clarification: – Fernando Rojo Jan 07 '20 at 19:20
3

can anyone clarify what does "drag React.xcodeproj from Libraries to root tree" mean. – Ali May 11 '20 at 06:00
The tree has a Libraries subfolder where the React.xcodeproj is - you need to move it to the root of the tree which you can via drag-and-drop. – agiaLab May 14 '20 at 11:26
1

No it doesnt have a libraries sub folder – Ackman Dec 06 '20 at 02:02
11

As React Native 0.64, there is no React.xcodeproj file anymore – Lopakhin Mar 29 '21 at 11:17
4

@Lopakhin - then how does one solve this issue for react-native > 0.64? I am having this exact issue and cannot find a solution. – Abram Jun 18 '21 at 09:23
18

There is no Build tab -> uncheck Parallelize Build any more but the bug is still there! – Macilias Sep 28 '21 at 19:55

score 36 · Answer 2 · answered Sep 20 '18 at 13:14

36

Make sure you disable Parallelise Build and add React target above your target

answered Sep 20 '18 at 13:14

onmyway133

45,645
31
257
263

Figured it out on my own after the first answer, but moving react up did the trick! Had to realize what that actually meant for the building process though – njoye Sep 26 '18 at 19:15
1

Was pulling my hair out and thinking what I was doing wrong after adding the React target but moving it up did the trick. @njoye could you explain what this means in the build process? Thank you! – Eugene Kim Oct 30 '18 at 05:58
@EugeneKim the order of elements in lists is Apple's way of showing chronological order (this still f*s me up often, on OSX as well as iOS). So putting the target "React" before "App" will build the code from "React" before your own. Since your own code uses the React target this seems to affect if it is able to be built. There are probably files being built that are then used in your target. – njoye Nov 12 '18 at 17:31
I want to use the parallel build feature to reduce the build time – utkarsh-devops Jul 30 '19 at 09:06

score 30 · Answer 3 · edited Aug 19 '19 at 15:32

30

QUICK FIX (not the best)

Change the import react-native header lines:

 #import <React/RCTBridgeModule.h>
 #import <React/RCTLog.h>

To:

 #import "RCTBridgeModule.h"
 #import "RCTLog.h"

Here is an example of changes I had to make for the library I was trying to use: Closes #46 - 'RCTBridgeModule.h' file not found.

edited Aug 19 '19 at 15:32

Iso

3,148
23
31

answered Jan 15 '17 at 17:24

Simar

2,475
5
16
19

18

If you read the release notes carefully, I think it's actually the other way -- the new / approved way is `#import `? [commit here](https://github.com/facebook/react-native/commit/e1577df1fd70049ce7f288f91f6e2b18d512ff4d) – user Jan 25 '17 at 15:29
2

I know it seems backwards to what the docs recommend, but the specified format `#import "RCTBridgeModule.h"` really did work better for me today. – paws Mar 16 '17 at 00:02
The error for me is flagged in the file RCTFileReaderModule.h. I changed the #import statement as suggested but it didn't help. I see in the linked repo pull request that the change was done in RNFSManager.h and RNFSManager.m. I tried making it in these two files but it didn't help either. Any idea what I am doing wrong? – Yossi Apr 27 '20 at 07:21
1

But my code is erroring out at `#import "RCTBridgeModule.h"`... – velkoon Aug 26 '21 at 19:19
[0.71] Do not use this method, all subsequent imports inside `React/*.h` now fails with not found. – Vicary Jan 26 '23 at 09:01

score 15 · Answer 4 · answered Jul 07 '18 at 21:09

15

Change

  #import "RCTBridgeModule.h"

to

 #import "React/RCTBridgeModule.h"

answered Jul 07 '18 at 21:09

Mantas Laurinavičius

941
12
23

score 4 · Answer 5 · answered Jul 15 '17 at 16:46

4

If Libraries/React.xcodeproj are red in xcode then reinstall node_modules

rm -rf node_modules && yarn

My newly created project from react-native 0.46.3 was red :S I have npm 5.3.0 and yarn 0.24.5 when I did react-native init

answered Jul 15 '17 at 16:46

Codler

10,951
6
52
65

Thank you, i was pushing my project to github. And when cloning it again i was missing the React libraries that were showing in red. your command is working. – Rifinio Jan 16 '18 at 16:04

score 4 · Answer 6 · answered Nov 23 '19 at 12:58

For me, this error occurred when I added a new scheme/target (app.staging) in the app and installed pods using pod install.

This issue is occurring due to pods are not shared for all targets. So I need to add newly added target (app.staging) inside the Podfile.

Here is my Podfile.

platform :ios, '9.0'
require_relative '../node_modules/@react-native-community/cli-platform-ios/native_modules'

target 'app' do
  # Pods for app
  pod 'FBLazyVector', :path => "../node_modules/react-native/Libraries/FBLazyVector"
  pod 'FBReactNativeSpec', :path => "../node_modules/react-native/Libraries/FBReactNativeSpec"

  target 'appTests' do
    inherit! :search_paths
    # Pods for testing
  end

  # Pods for staging app // important line below
  target 'app.staging'

  use_native_modules!
end

Helped me! I needed also to clean project after pod install – chenop Dec 24 '20 at 22:51 — chenop, Dec 24 '20 at 22:51

score 4 · Answer 7 · answered Feb 23 '20 at 20:01

4

I ran into this issue after doing a manual react-native link of a dependency which didn't support auto link on RN 0.59+

The solution was to select the xcodeproj file under the Libraries folder in Xcode and then in Build Settings, change Header Search Paths to add these two (recursive):

$(SRCROOT)/../../../ios/Pods/Headers/Public/React-Core
$(SRCROOT)/../../../ios/Pods/Headers/Public

answered Feb 23 '20 at 20:01

qwertzguy

15,699
9
63
66

1

this solved my problem, I think the old solutions(linking React.xcodeproj etc) don't work anymore, this one is the correct solution. – Tarun Gupta Apr 02 '22 at 16:44
1

That worked for me too, wasted some time on this one.. Should be the selected answer in 2022 when humanity divided to projects in > 0.59 and < 0.59 – Blue Bot Oct 25 '22 at 16:46

score 3 · Answer 8 · answered Feb 18 '17 at 04:09

3

For viewers who got this error after upgrading React Native to 0.40+, you may need to run react-native upgrade on the command line.

answered Feb 18 '17 at 04:09

Lawrence

10,142
5
39
51

5

I'm trying this right now. What about using [react-native-git-upgrade](https://github.com/facebook/react-native/tree/master/react-native-git-upgrade) instead? – pgarciacamou Feb 21 '17 at 17:32
Right, that's the other option. I think they'll both work. – Lawrence Feb 21 '17 at 21:12

score 3 · Answer 9 · answered Apr 15 '21 at 13:24

3

My solution was to remove everything in Libraries like described here

answered Apr 15 '21 at 13:24

redexp

4,765
7
25
37

This worked for me, thank you so much! By the way, @redexp if possible can you please explain what was the issue exactly? Because I have no idea about cocoapods and xcode – Shubham Bisht Apr 22 '22 at 15:39

score 2 · Answer 10 · answered Jan 18 '17 at 19:23

Latest releases of react-native libraries as explained in previous posts and here have breaking compatibility changes. If you do not plan to upgrade to react-native 0.40+ yet you can force install previous version of the library, for example with react-native-fs:

npm install --save -E react-native-fs@1.5.1

score 2 · Answer 11 · answered Jun 27 '17 at 05:27

2

I was able to build a debug, but I was unable to build an archive.

I solved this issue by dragging React.xcodeproj found in /node_modules/react-native/React to my root directory in Xcode, then added React as a target dependancy in build phases > target dependencies.

answered Jun 27 '17 at 05:27

BuffMcBigHuge

579
5
8

1

There's no `React.xcodeproj` in `/node_modules/react-native/React`. – Andrew Koster Apr 21 '20 at 02:54
1

@AndrewKoster I am experiencing the same issue – Steven Matthews Apr 21 '20 at 05:18
@CecilRodriguez I've managed to fix this when compiling in Xcode, by adding Cocoapods and adding React as a pod in the Podfile. However, once I try to use the compiled library in `react-native run-ios`, I get compilation errors that don't happen in Xcode. The complete lack of relevant documentation is frustrating. – Andrew Koster Apr 21 '20 at 19:10
@CecilRodriguez have you found a solution? – Yossi Apr 27 '20 at 07:53
@AndrewKoster so inside Xcode it does work? If it does, can you explain in more details what you did? – Yossi Apr 27 '20 at 07:55
1

@Yossi No, not yet. All of the attempts I've tried haven't worked. – Steven Matthews Apr 27 '20 at 17:32
1

@Yossi No, I tried yours. No luck. It has something to do with my native module I think – Steven Matthews Apr 27 '20 at 18:29

score 2 · Answer 12 · answered Jan 22 '20 at 20:56

After React Native 0.60 this issue is often caused by a linked library mixed with the new 'auto-linking' feature. This fixes it for me

Unlink old library using

$ react-native unlink react-native-fs

Refresh Pods integration entirely using

$ pod deintegrate && pod install

Now reload your workspace and do a clean build.

score 2 · Answer 13 · answered Jan 23 '20 at 17:19

2

I receive this error in any new module I create with create-react-native-module. None of the posted solutions worked for me.

What worked for me was first making sure to run yarn in the newly created module folder in order to create node_modules/ (this step is probably obvious). Then, in XCode, select Product -> Scheme -> React instead of the default selection of MyModuleName.

answered Jan 23 '20 at 17:19

Taylor Kline

908
3
9
30

+1, it's important to add for others new to module development that you won't see the other schemes until you create a valid podfile and run `pod install`. create-react-native-module does not appear to do this for you. Got me hung up for a while. But this worked for me once I created a valid podfile and ran the install. – Elliot Rodriguez Feb 15 '20 at 13:44
@ElliotRodriguez is the Podfile from the example/ios folder acceptable for a library itself? – Vyacheslav Orlovsky Aug 07 '22 at 10:40

score 2 · Answer 14 · answered Oct 26 '22 at 06:21

2

delete the pods folder and the .xcworkspace file
run pod install again in that directory
try to archive again and done

answered Oct 26 '22 at 06:21

FaysalB

330
1
11

score 1 · Answer 15 · answered Jul 10 '19 at 17:07

This error appeared for me after I ran pod install command for the new dependencies. Along with those, React had also been installed. Therefore probably Xcode was confused for path. I removed these lines from PodFile and error was gone. Please note that those removed from here were already linked in Xcode.

target 'app' do

  pod 'GoogleMaps'
  pod 'Firebase/Auth', '~> 6.3.0'
  pod 'Firebase/Database', '~> 6.3.0'

  # Removed four pods below and it worked.

  pod 'react-native-image-picker', :path => '../node_modules/react-native-image-picker'

  pod 'ReactNativePermissions', :path => '../node_modules/react-native-permissions'

  pod 'react-native-image-resizer', :path => '../node_modules/react-native-image-resizer'

  pod 'RNFS', :path => '../node_modules/react-native-fs'

  end

score 1 · Answer 16 · edited Feb 04 '20 at 13:38

Go to iOS folder in your project and install pod -

$ pod install

If you are getting any error in installation of pod type command-

$ xcode-select -p

Result should be - /Applications/Xcode.app/Contents/Developer

If the path is incorrect then open your iOS project in Xcode and go to: Xcode->preferences->command line tools-> select Xcode

And again install the pod your issue will be fixed.

score 1 · Answer 17 · answered Apr 27 '20 at 10:18

1

anhdevit's suggestion in https://github.com/facebook/react-native/issues/24363#issuecomment-488547280 worked for me:

In your terminal, run: defaults delete com.apple.dt.Xcode

answered Apr 27 '20 at 10:18

Yossi

5,577
7
41
76

score 0 · Answer 18 · answered Mar 26 '19 at 09:22

0

If you want to make it from your editor also open SMobile.xcscheme

And change parallelizeBuildables = "NO"

answered Mar 26 '19 at 09:22

Hadnazzar

1,517
19
21

kodeusz · Answer 19 · 2019-05-16T08:01:36.953

0

For me didn't work any from the above solutions and below it is what worked (I had already checked out Parallelize Build and added React)

1. Open XCode --> To Libraries add `$LibraryWhichDoesNotWork.xcodeproj$`
2. Then for your app in the `Build Phases` add to the `Link Binary with Libraries` the file `lib$LibraryWhichDoesNotWork$.a`

edited May 16 '19 at 08:01

answered May 16 '19 at 07:34

kodeusz

178
3
10

score 0 · Answer 20 · answered Jul 26 '19 at 11:35

I've encountered this issue while upgrading from 0.58.4 to new react-native version 0.60.4. Nothing from what i found on the internet helped me, but I managed to get it working:

Go to build settings, search for 'Header search paths', select the entry, press DELETE button.

I had these values overriden, and looks like they fell back to defaults after deletion. Also Cocoapods was complaining about it with messages in Terminal after pod install:

[!] The `app [Release]` target overrides the `HEADER_SEARCH_PATHS` build setting defined in `Pods/Target Support Files/Pods-app/Pods-app.release.xcconfig'. This can lead to problems with the CocoaPods installation

score 0 · Answer 21 · answered Mar 17 '20 at 13:15

If you want to keep Parallelise Build enabled and avoid the missing header problems, then provide a pre-build step in your scheme to put the react headers into the derived-data area. Notice the build settings are coming from the React project in this case. Yes it's not a thing of beauty but it gets the job done and also shaves a lot of time off the builds. The prebuild step output ends up in prebuild.log. The exact headers you'll need to copy over will depend on your project react-native dependencies, but you'll get the jist from this.

Get the derived data directory from the environment variables and copy the required react headers over.

#build_prestep.sh (chmod a+x)
derived_root=$(echo $SHARED_DERIVED_FILE_DIR|sed 's/DerivedSources//1')
react_base_headers=$(echo $PROJECT_FILE_PATH|sed 's#React.xcodeproj#Base/#1')
react_view_headers=$(echo $PROJECT_FILE_PATH|sed 's#React.xcodeproj#Views/#1')
react_modules_head=$(echo $PROJECT_FILE_PATH|sed 's#React.xcodeproj#Modules/#1')
react_netw_headers=$(echo $PROJECT_FILE_PATH|sed 's#React/React.xcodeproj#Libraries/Network/#1')
react_image_header=$(echo $PROJECT_FILE_PATH|sed 's#React/React.xcodeproj#Libraries/Image/#1')

echo derived root = ${derived_root}
echo react headers = ${react_base_headers}

mkdir -p ${derived_root}include/React/

find  "${react_base_headers}" -type f -iname "*.h" -exec cp {} "${derived_root}include/React/" \;
find  "${react_view_headers}" -type f -iname "*.h" -exec cp {} "${derived_root}include/React/" \;
find  "${react_modules_head}" -type f -iname "*.h" -exec cp {} "${derived_root}include/React/" \;
find  "${react_netw_headers}" -type f -iname "*.h" -exec cp {} "${derived_root}include/React/" \;
find  "${react_image_header}" -type f -iname "*.h" -exec cp {} "${derived_root}include/React/" \;

The script does get invoked during a build-clean - which is not ideal. In my case there is one env variable which changes letting me exit the script early during a clean.

if [ "$RUN_CLANG_STATIC_ANALYZER" != "NO" ] ; then
    exit 0 
fi

score 0 · Answer 22 · answered Jul 12 '22 at 20:03

react-native version 0.67.4 (recently updated) This build error started to show up in ios.

I found under my project > Edit Scheme > Build

There was a reference to "React" but it indicated "Missing"

So I removed it (little - button) and added React back (little + button) via the popup which has a Pods folder and a "React" pod project present.

So it looks like react-native used to supply a project file that you would set as a build target in the scheme: /node_modules/react-native/ReactReact.xcodeproj

However with this newer version of react that project is not present, which would explain why building will fail if you have a native module bridge (its searching for header files that don't exist)

I no longer get the build error, but I haven't verified it works. Will update once I get a positive outcome (or a negative one for that matter). Even if this does fix it, I am not sure if this is the "right" way, but I'm certainly open to suggestions.

score 0 · Answer 23 · answered Aug 17 '22 at 20:25

0

In my case, the wrong target was selected in podfile, after correcting that, I was good to go.

answered Aug 17 '22 at 20:25

Musab Gulfam

126
1
7

score 0 · Answer 24 · answered Sep 19 '22 at 14:40

0

In my case, I removed the 'arm64' from the release section located under Excluded architectures in the targets project

answered Sep 19 '22 at 14:40

Kingsley Akpan

213
3
3

score -3 · Answer 25 · edited Jul 04 '17 at 11:13

-3

What you can do to get it right is:

1) npm uninstall reat-native-fs to uninstall library

2)npm unlink react-native-fs to unlink the library

Now the library is successfully removed and now install the lib again in your project and this time link everything manually. Sometime automatic linking causes this error.

edited Jul 04 '17 at 11:13

Håken Lid

22,318
9
52
67

answered Jan 15 '17 at 16:00

Codesingh

3,316
1
11
18

`React/RCTBridgeModule.h` file not found

25 Answers25

Linked