-
Notifications
You must be signed in to change notification settings - Fork 626
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Apple M1] Don't compile on IOS metro-hermes-compiler too many open files #668
Comments
+1 i also get this error on M1
|
Same problem |
try deleting the yarn.lock file and peforming |
// yarn.lock
fsevents@^2.1.2:
- version "2.1.3"
- resolved "https://registry.yarnpkg.com/fsevents/-/fsevents-2.1.3.tgz#fb738703ae8d2f9fe900c33836ddebee8b97f23e"
- integrity sha512-Auw9a4AxqWpa9GUfj370BMPzzyncfBABW8Mab7BGWBYDj4Isgq+cDKtx0i6u9jcX9pQDnswsaaOTgTmA5pEjuQ==
+ version "2.3.2"
+ resolved "https://registry.yarnpkg.com/fsevents/-/fsevents-2.3.2.tgz#8a526f78b8fdf4623b709e0b975c52c24c02fd1a"
+ integrity sha512-xiqMQR4xAeHTuB9uWm+fFRcIOgKBMiOBP+eXiyT7jsgVCq1bkVygt00oASowB7EdtpOHaaPgKt812P9ab+DDKA== |
@JonnyBurger @owinter86 fsevents upgrade to 2.1.3 works like a charm, many thanks. |
only doing this does not always help |
you save me, tks bro! |
not working, after reinstall 'watchman', upgrade fsevent. it can be debug on simulator, but not archive. any solution? |
node version v12, v14, v16, v18 all failed. |
upgrading my output is
|
Same here, on M1 Pro, Ventura 13, XCode 14.1 |
There are a couple of issues conflated here I think.
Use a combined kqueue+fsevents watcherNewer versions of Watchman allow the use of a combined FSEvents + kqueue watch strategy to reduce the load on FSEvents (similar to newer versions of Node's {
"watcher": "kqueue+fsevents"
} Verify that you're using this watcher backend with Raise system limits on open file descriptorsEnsure you are using Watchman, and follow instructions below to raise the watch limits on your machine:
Source: https://facebook.github.io/watchman/docs/install.html#macos-file-descriptor-limits |
|
@skanger did you find any solution? |
Tried everything and realized there was no fsevents in my node_modules (even though it's a newly properly created react native project), did 'npm install fsevents' and this solved the issue. |
Thanks, it works for me on rn v.0.74 and node 18.14.2 |
Running into this again on node 20, any new fix in 2024? |
Thanks, it works for me on rn v.0.75.3 and node 20.17.0. |
Bug Description
Steps To Reproduce
The Expected Behavior
Pre-version compiles fine
Error Message
Additional Info
Newly created React Native project is being compiled successfully. The issue only with a existing project.
The text was updated successfully, but these errors were encountered: