-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RCTPushNotificationManager.h:8:9: fatal error: 'React/RCTEventEmitter.h' file not found #1144
Comments
Looks like this Stack Overflow question solves the issue. The trick, as mentioned by Chris in the comments of the SO question is to add the following to your Podfile:
It looks like this might be something new to React .60; should these instructions perhaps be in the README? |
@stevenleeg after adding those lines, the RTC is gone, but I get:
:( |
Here is what worked for me: Copy In the root folder of your project:
Don’t know if that is a good solution. Maybe if someone could explain me why it was not in there in the first place? I followed the setup instructions 1 by 1 very carefully doing everything right… Thank you |
I've spent some time on this and found out that after adding Maybe someone else can confirm if this works for them as well? |
I can confirm @Jordanwmk that in a newly init'd RN app, I followed all the same steps from the README in addition to adding the line in the podfile EXCEPT I avoided adding libRCTPushNotification.a to Link Binary With Libraries. After doing this the app successfully built. I haven't tested the notifications yet but the building successfully is farther than I've gotten so far haha. |
Add this to the Podfile |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 30 days if no further activity occurs. Thank you for your contributions. |
Hi there,
After manually linking react-native-push-notification as per the documentation I've found myself running into this issue on a freshly
init
'd React Native project:Any ideas as to what might be causing this? I've seen the issue arise from a few other projects, along with a similar report from this project in this stack overflow question.
The text was updated successfully, but these errors were encountered: