React-native-fcm: RNFIRMessaging.h file not found

[Tiagojdferreira]

After doing the pod install I get the error "RNFIRMessaging.h" file not found.

[Tiagojdferreira]

If someone has the same problem, the solution is doing:

npm install

[cpsiaki]

I'm still having trouble with this. Do I need to add the xcode project to the libraries folder and link in build phases?

I think I'm missing steps here but don't know what. I just get file not found every time.

[jondbm]

I'm having this problem too. This is such a difficult library to get working. I've tried a fresh npm install, running and re-running Cocoapods, different combinations of the config file, nothing seems to work.

[cpsiaki]

Hi Jon, I figured out my problem. Similar to what you do for PushNotificationsIOS RN API, you need to add '$(SRCROOT)/../node_modules/react-native-fcm/ios' to header search paths in build settings. That's what I was missing I hope they update the readme.

[jondbm]

Wow thanks, that seems to work and has saved my day! I would never have figured that out, thank you so much.

[amanthegreatone]

Started a new project with RN 0.40.0 and found the same issue after following all instructions for installation. I think the documentation should be updated with this issue. Not sure if this happens for everyone creating new projects.

@cpsiaki thanks for the tip.

[mantap123]

phew... It seems the react-native link command missed to add header search path...

[ynnckcmprnl]

@amanthegreatone, I can confirm I also had to add the header search path manually for a clean install with RN 0.40.

[oliversisson]

When you write
you need to add '$(SRCROOT)/../node_modules/react-native-fcm/ios' to header search paths in build settings.
I'm not a iOS developer. What does this mean? Do you have to open the project up in Xcode (which doesn't seem to be working for me) or can I just add this to some file?

[oliversisson]

It seems like these are the appropriate steps.

1. Open ios directory in Xcode
2. Click your project name on the left there.
3. Click Building Settings. Click All.
4. Scroll down to Header Search Paths.

[jondbm]

@oliversisson You're correct, those are the steps, the quickest way to get XCode up and running is to open the ios folder in your app, and in there there should be a [myproject].xcworkspace file. Open that, and it should automatically open your project in XCode, and you can then navigate to the build settings, make the changes, then clean and build the project and run on any simulators or devices you need.

Although the source code of your app is written in React Native, the built XCode project is like any other iOS project so if you get stuck there are lots of general XCode tutorials out there to help with navigating around and getting things up and running.

[jordanmkoncz]

Thanks @cpsiaki. I had the same issue and your suggestion fixed it for me too.

[mypark]

This issue should still be open no? Seems like the readme should be updated with these instructions or react-native link should do this step?

[leonardobazico]

Any updates about @mypark said?

[yjb94]

This is because of linking. Better solving by
react-native link react-native-fcm

[austincline09]

None of these solutions seemed to fix the issue for me. However with my AppDelegate.m file opened in Xcode, on the right side under Target Membership I had MyProject and MyProjectTests both checked. Once I unchecked MyProjectTests the issue went away and my app was able to build

[luisbajana]

If you're archiving make sure you also add '$(SRCROOT)/../node_modules/react-native-fcm/ios' under Release.

[W0404768]

hi but it did not solve my problem, any other idea?!