React Native iOS build failed because "'simdjson.h' file not found"

See original GitHub issue

I’m not sure what’s going on. My RN version is 0.64.2, watermelondb version is 0.23.0-9

Screen Shot 2021-06-24 at 8 52 06 AM

Issue Analytics

State:
Created 2 years ago
Comments:18 (1 by maintainers)

Top GitHub Comments

5reactions

jamesjlvcommented, Dec 2, 2021

Hello guys,

This is what’s worked for me:

Go to node_modules/@nozbe/simdjson/src
- Copy those 2 files “simdjson.cpp” and “simdjson.h”

Captura de Tela 2021-12-02 às 00.41.08.png

Go to node_modules/@nozbe/watermelondb/native/shared
- Paste the files that you copied above “simdjson.cpp” and “simdjson.h”

Captura de Tela 2021-12-02 às 00.39.50.png

Execute the comand yarn run ios , for me worked.

Make sure that you edited your podfile and write the 2 lines below:

    pod 'React-jsi', :path => '../node_modules/react-native/ReactCommon/jsi', :modular_headers => true
    pod 'simdjson', path: '../node_modules/@nozbe/simdjson'

_Font: https://nozbe.github.io/WatermelonDB/Installation.html_

Some erros shows up, and this is how I fix:

In the first time, I got a message (fatal error: malformed or corrupted AST file…), with this, I have to go in the /Users/YOURUSERNAME/Library/Developer/Xcode/DerivedData and clean all the files in this folder before a try to make a new compilation.
To make sure that everything will works well, I deleted my folder Pods inside tha “ios” folder, and after I execute the command pod install to build this folder again. (Make sure you have the backup)
I deleted my folder node_modules to and download again with the command yarn install.

I hope this helps someone, bye bye 😉

3reactions

renatobentorochacommented, Oct 20, 2022

Hello guys,

This is what’s worked for me:

Go to node_modules/@nozbe/simdjson/src

Copy those 2 files “simdjson.cpp” and “simdjson.h”

Go to node_modules/@nozbe/watermelondb/native/shared

Paste the files that you copied above “simdjson.cpp” and “simdjson.h”

Execute the comand yarn run ios , for me worked.

Make sure that you edited your podfile and write the 2 lines below:
    pod 'React-jsi', :path => '../node_modules/react-native/ReactCommon/jsi', :modular_headers => true
    pod 'simdjson', path: '../node_modules/@nozbe/simdjson'
_Font: https://nozbe.github.io/WatermelonDB/Installation.html_

Some erros shows up, and this is how I fix:

In the first time, I got a message (fatal error: malformed or corrupted AST file…), with this, I have to go in the /Users/YOURUSERNAME/Library/Developer/Xcode/DerivedData and clean all the files in this folder before a try to make a new compilation.

To make sure that everything will works well, I deleted my folder Pods inside tha “ios” folder, and after I execute the command pod install to build this folder again. (Make sure you have the backup)

I deleted my folder node_modules to and download again with the command yarn install.

I hope this helps someone, bye bye 😉

Hi @jamesjlv thanks a lot by the solution. I have added a little command at xcode that did the same that you did.

Captura de Tela 2022-10-19 às 10 45 59

Top Results From Across the Web

`React/RCTBridgeModule.h` file not found - Stack Overflow

In my case this particular problem happened when I was trying to archive a 0.40+ react-native app for iOS (solution was found here:...

Installation - WatermelonDB documentation

iOS (React Native) · Open ios/YourAppName.xcodeproj in Xcode · Right-click on (your app name) in the Project Navigator on the left, and click...

iOS Native Modules

The first step is to create our main custom native module header and implementation files. Create a new file called RCTCalendarModule.h.

React Native SDK Troubleshooting - Visual Studio App Center

'React/RCTDefines.h' file not found; React Native link command unrecognized; Build error such as 'AppCenterCrashes/MSACErrorReport.h' file ...

'RCTLog.h' file not found & Us… | Apple Developer Forums

The technical issue is as follows: it seems to be appearing in the RNBranchConfig.m file within the react-native-branch package for iOS specifically in...