RCTJSEnvironment.h file not found after upgrade to react-native 0.47.0

[tjmadsen]

Everything is working in 0.46.0, but after upgrading to 0.47.0 (both by manually upgrading the package and by using react-native-git-upgrade), getting this error.

Environment

1. react-native -v: 0.47.0
2. node -v: 8.2.1
3. npm -v: 5.3.0
4. yarn --version: 0.21.3
   

Then, specify:

• Target Platform: iOS

• Development Operating System: macOS

• Build tools: Xcode (iOS)

Steps to Reproduce

Upgrade to react-native 0.47.0 and run react-native run-ios

Expected Behavior

App should build and run successfully

Actual Behavior

[AlanFoster]

@tjmadsen Sanity test question; Did you run a yarn / do a clean / clear caches etc?

[tjmadsen]

@AlanFoster Yes, did a cache clean, did a fresh yarn/npm install

In addition, I tried troubleshooting with a number of versions, and other dependencies. I wasn't able to make much progress other than to further isolate the issue down to the single switch between 0.46.0 and 0.47.0

I'm still in active dev with the app, so I'll continue to test upgrading and add any more information I can.

[zaiz91]

I got the same error, after upgrading to 0.47. @tjmadsen Any progress on this issue?

[fbacker]

Same issue after an upgrade. Any success for anyone?

"react-native": "0.47.1"

When browsing the RCTDevSettings.mm I can hyperclick to the file

/React/Base/RCTJSEnvironment.mm but still getting the error.

I've also tried to clean house without success with:

npm cache clean --force 
watchman watch-del-all 
rm -fr $TMPDIR/react-* && rm -rf node_modules 

[zaiz91]

The following workend for me:

• Clean Xcode Project
• Delete Pod Files & pod.lock
• Delete node_modules & yarn.lock
• fix possible bugs in js code
• yarn install
• pod installl

Good luck.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions.