#import <React/RCTEventEmitter.h> not found

[ease-space]

[say95]

Hey @maystrenkoYurii , I am facing the same issue. Are you able to resolve this issue?

[opiruyan]

What is your RN version? 61? Does your Podfile conform to required?

[say95]

@opiruyan Hey, my RN version is 0.59.5. I somehow able to fix it by modifying the pod file

# Uncomment the next line to define a global platform for your project
# platform :ios, '9.0'

target 'pushnotifications' do
  pod 'React', :path => '../node_modules/react-native'
  pod 'yoga', :path => '../node_modules/react-native/ReactCommon/yoga'
  pod 'RNCPushNotificationIOS', :path => '../node_modules/@react-native-community/push-notification-ios'

  post_install do |installer|
    installer.pods_project.targets.each do |target|
      if target.name == "React"
        target.remove_from_project
      end
    end
  end
end

[guopeng1994]

same issues in RN 0.59.9

[BrandonMHogan]

same issue using expo 35.0.0 Was working with expo 33.0.0, but stopped after updating.

Was able to get it compiling by adding the following to the Header Search Paths for the RNCPushNotificationIOS Target in the PushNotificationIOS project .xcodeproj. Make sure they are its marked as recursive.

"$(SRCROOT)/../../../../ios/Pods/Headers/Public/React" "$(SRCROOT)/../../../react-native/ReactCommon/yoga"

[muriloribeiro34]

use --> cd ios && pod install

[GregoryBabonaux]

Same issue with RN 0.59.10

i tried pod install with no success

[muriloribeiro34]

pod install so it works in react-native 0.60+, sorry

[GregoryBabonaux]

pod install so it works in react-native 0.60+, sorry

Yep, it probably work for RN 0.60+, but the major issues related here are for RN 0.59.x

[caner-karaman]

Same issue after upgrading RN 0.61.3

[cx5168]

RN0.61.4 same issue!!!

[cx5168]

I m solved it!

1. Libraries→PushNotificationIOS.xcodeproj→build setting→Search Paths→Header Search Paths: $(SRCROOT)/../../../../ios/Pods/Hearders/Public

2. menu(Product)→Scheme→Edit Scheme: [+]→Pods→React

3. clean→build

[Naturalclar]

@maystrenkoYurii has this issue been solved for you? If so, I'll go ahead and close this issue :)