-
Notifications
You must be signed in to change notification settings - Fork 629
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
Error: EMFILE: too many open files, watch #1405
Comments
Fixed it by upgrading all the packages (except react, kept it at 18.x as react native doesn't support 19.x yet), though my packages were just a little behind the latest versions, it worked, deleted node_modules, pods and resintalled them . |
@Irfanwani I am getting the same error (unable to make archieve) as you mentioned. Below is the package.json and react-native info I am using. Can you please help me what I am missing here?
|
@codingslash76 for me it was the packages, delete node_modules, upgrade your packages, delete pods and reinstall all dependencies (npm i, cd ios, pod install). It should fix the issue |
@Irfanwani Thanks for the response. I have attempted all the steps multiple times without success, even after resetting the entire system. I have created the following issue. |
Did you reinstalled watchman (and delete its cache). |
Yes, Multiple times. |
Bug Report
I upgraded the app to the new arch (0.76.x) and now I am getting this error when trying to archive in xcode:
What is the current behavior?
App works fine, in dev as well as in release mode on both android as well as in iOS. First i was getting this error in terminal too when running
npm start
but that was fixed by deleting node_modules and reinstalling deps but archiving is still throwing this error.If the current behavior is a bug, please provide the steps to reproduce and a minimal repository on GitHub that we can
yarn install
andyarn test
.Set Run scheme to Release and change run destination to Any iOS device, and try to archive.
What is the expected behavior?
Archive should be executed successfully instead of throwing a metro bundler error.
Please provide your exact Metro configuration and mention your Metro, node, yarn/npm version and operating system.
metro - v0.81.0
node - v22.11.0
npm - v10.9.0
react-native - 0.76
The text was updated successfully, but these errors were encountered: