Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Can't find ”RCTAssert.h” while compiling after freshly generated project on v0.10.0

See original GitHub issue

It seems there’s an error in v0.10.0 that causes application generated with react-native init to not be compilable immediately. The fix is to open <AppName>.xcodeproj/project.pbxproj and find and replace any mention of "$(SRCROOT)/node_modules/react-native/React/**" with "$(SRCROOT)/../node_modules/react-native/React/**" (note the ..)

Issue Analytics

State:
Created 8 years ago
Comments:22 (8 by maintainers)

Top GitHub Comments

2reactions

brenmcnamaracommented, Aug 27, 2015

The problem for me was that the Test Target had an incorrect Header Search Path. This can be fixed by going into xcode, selected the Test Target, going to build Settings, going into the section “Search Paths”.

Inside this “Search Paths” section, there is a “Header Search Paths” attribute, select it and make sure there is a search path: $(SRCROOT)/…/node_modules/react-native/React set to Recursive. MAKE SURE THE “…” is present after $(SRCROOT) or it will be looking in the wrong directory. MAKE SURE YOU’RE LOOKING IN THE TEST TARGET, NAMED {YOURAPP}Tests

screen shot 2015-08-27 at 9 41 44 am

0reactions

LuongTruongcommented, Jun 20, 2018

@brenmcnamara Thank you, your solution help me to fix this. I do not know why in year 2018, this problem still occur 😦 so sad

Top Results From Across the Web

Newest 'react-native' Questions - Page 2544 - Stack Overflow

React-native Xcode build fails -> 'RCTAssert.h file not found' ... After installing react native in the terminal and I created projects according to...