'React/RCTRootView.h' file not found

[YYL1999]

l cannot run the project,because 'React/RCTRootView.h' file not found.so what should l do??

[react-native-bot]

Thanks for submitting your issue. Can you take another look at your description and make sure the issue template has been filled in its entirety?

👉 Click here if you want to take another look at the Bug Report issue template.

[RyanElliott10]

Try building React before the entire project. This may also be an issue with how you have your build scheme setup -- make sure to have Parallelize Build unselected.

Xcode -> Project Scheme -> Manage Schemes -> Double Click on yours -> Build -> Uncheck Parallelize Build

[akaralar]

I faced the same issue. Tried building React first but it didn't fix the issue. Parallelize Build is unselected as well.

I faced this issue when I tried to install react-native-fbsdk via cocoapods. Not only with react-native-fbsdk but some other packages had similar errors, files not found that belong to the React project. The common thing among these libs were that I was installing them with Cocoapods (as per the result of react-native link <package>. Cocoapods installs a version of React where there is only a Core folder in the pod, and the files not found were present in other folders in React included in the main project. I worked around the issue by linking manually instead of installing with cocoapods.

[YYL1999]

Schemes

thanks .I redesigned a project that has been solved.

[YYL1999]

我遇到了同样的问题。先尝试建筑，React但没有解决问题。Parallelize Build也是未被选中的。

当我尝试react-native-fbsdk通过cocoapods 安装时，我遇到了这个问题。不仅有react-native-fbsdk一些其他包有类似的错误，找不到属于该React项目的文件。这些库中常见的事情了，我是用的CocoaPods（安装它们按的结果react-native link <package>。的CocoaPods安装某个版本的React那里是只有Core在群文件夹，并在未找到的文件存在于其他文件夹React包含在主要项目。我通过手动链接而不是用cocoapods安装来解决这个问题。

I redesigned a project that has been solved.thanks

[michalchudziak]

Hello there 👋 this issue doesn't have a repro (which means, a react-native init-ed project with the minimal changes that leads to creating the same issue you are reporting). Unfortunately, I have no way of helping you in a meaningful way – there is no easy way for me to recreate the situation and check that the issue reported is still there when changing the code.

Because of this, we are going to close this issue - but if a repro is shared, we are happy to reopen it 🤗