React-native-firebase: 'FirebaseInstanceID/FIRInstanceID.h' file not found from 3.0.0-alpha.5 to 3.0.0

[brianhiss]

Issue

Hey guys, wondering if anyone else is seeing the same issue as I am. I've been playing with this the last two days are narrowed it down to this commit.

It's in: ios/RNFirebase/messaging/RNFirebaseMessaging.m adding #import <FirebaseInstanceID/FIRInstanceID.h>. It was added for this PR.

When I upgraded from [email protected] to react-native-firebase 3.0.0, I couldn't compile. I checked Header Search Paths, made sure the FirebaseInstanceID.framework is as expected. I cannot seem to get it to compile with this commit.

If I comment out the #import <FirebaseInstanceID/FIRInstanceID.h>, I can get react-native-firebase 3.0.0 to compile and run great. Otherwise, I can downgrade back to [email protected] and it compiles again.

FIRInstanceID.h looks like a Swift file. Does this mean it requires # use_frameworks! uncommented in the Podfile?

Anyone else experiencing this? Appreciate any insight.

Environment

1. Application Target Platform: iOS 11
2. Development Operating System: macOS Sierra 10.12.6 (16G29)
3. Build Tools: Xcode 9.0
4. React Native version: 0.49.1
5. RNFirebase Version: 3.0.0
6. Firebase Module: Messaging (deleteInstanceId)

[SteffeyDev]

I found you can fix this by going to your project in the left hand side (not Pods), -> Libraries -> RNFirebase.xcodeproj -> Build Settings -> Framework Search Paths -> Add FIrebaseInstanceID (seemed to be missing there but you can add in the same format as the other ones). I was wondering why this didn’t work as well but it’s hit or miss for me.

[brianhiss]

@SteffeyDev Thank you for the quick response. I'm not using Codepush.xcproj, don't think that's a requirement for react-native-firebase.

My Framework Search Paths already include the reference to FirebaseInstanceID.

[SteffeyDev]

Oh sorry I put the wrong library name (I had issues with both), but you’re right, you do have it where it’s supposed to be. It’s odd because I had the expect same issue but I guess your problem lies elsewhere. Maybe check you header search paths?

[brianhiss]

@SteffeyDev I added my Header Search Paths, was playing in there as well. Attaching in case there is anything abnormal.

This was a brand new project today, react-native init MyProject, so it's a fresh 0.49.1, fresh node_modules and pod install, so wouldn't think there would be legacy conflicts.

I did set FirebaseInstanceID in the Framework Search Paths to recursive and that will let me build it.

Is anyone else seeing this on a new project, or old one?

[chrisbianca]

I think this may be an issue our end. I've just pushed a possible fix to ensure that FIRInstanceID is included in the library's framework search paths.

Could one of you try installing the latest version of the repo by running:

npm install --save https://github.com/invertase/react-native-firebase.git

And let me know if that resolves the issue?

[brianhiss]

@chrisbianca That seems to have worked for me.

I did a Clean Build Folder, yarn add https://github.com/invertase/react-native-firebase.git and pod update to make sure nothing was cached.

Thanks for jumping on that!

[chrisbianca]

No problem - we'll get it included in a release very soon. Just trying to get a few more bits in first...

[bramski]

Trying to use RNFirebase 3.3.1 I see this issue... any fix?

[f6m6]

I'm seeing this in react-native-firebase 5.0.0

[cmcaboy]

I am also getting this issue with version 4.2.0

[krimani]

$ pod update FirebaseInstanceID
just updating particular pod solved the same issues.

[tlynchlaw]

I experienced this same problem on April 11, 2019. Update did not work. But deintegrating the firebase pods with a pod deintegrate and then reinstalling with a pod install solved the problem.

[allanzi]

Thanks @tlynchlaw
Worked for me

[nthrussell]

Thanks @tlynchlaw
Worked for me as well, brilliant