react-native run-ios fails: ENOENT no such file or directory, uv_chdir

Created on 4 Dec 2016  路  18Comments  路  Source: facebook/react-native

I realize this has been asked before. #5054. That issue was closed. None of the fixes in there work for me.

Description

When I pull a repo, npm install then start the packager then run react-native run-ios it fails with error: ENOENT no such file or directory, uv_chdir

Reproduction

Cloned this repo: https://github.com/jcollum/kishar-nine

npm install
start packager (last line: [12/4/2016, 11:31:46 AM] <END> Initializing Packager (336ms) so it looks like it started fine

then:

$ react-native run-ios

ENOENT: no such file or directory, uv_chdir

Attempted fixes:

rm -rf node_modules
npm install 
rm -fr $TMPDIR/react-*
watchman watch-del-all
rm -fr $TMPDIR/npm*
rm -fr $TMPDIR/*.json.gzip
cat rn-cli.config.js 
# result: no file present

react-native run-ios 
# fails, same error

Solution

Give some indication of what the real issue is. Is there a missing folder? Seems so, but shouldn't run-ios be creating it?

Additional Information

$ react-native --version
react-native-cli: 1.2.0
react-native: 0.38.0

Platform: ios

Operating System: OSX: Darwin Darwin Kernel Version 15.6.0

iOS Stale

Most helpful comment

For me I just do a react-native upgrade then react-native run-ios and it works

All 18 comments

experience similar issue

Sorry I forgot to update: my issue was that I hadnt put my ios folder into source control. That missing uv_chdir error means it can't find any ios files.

Any updates on this? We just updated our Xcode today to Version 8.2.1 (8C1002), and now we're also seeing this issue. As feedback, actually naming the missing "file or directory" instead of just saying "no such file or directory" would be more helpful for us to diagnose the actual problem!

same here

Update (2017-Feb-21)

my problem solved, I forget how.
I think I close the proxy software and problem was gone. (Shadowsocks)

Seeing the same when following the Integration With Existing Apps guide http://facebook.github.io/react-native/releases/0.42/docs/integration-with-existing-apps.html

try running react-native init aProjectName if you are forkinga n existing project and trying to run/test in simulator @1c7 @pbojinov @gen4sp

@dereknex you're right, issue was with Info.plist.

I was editing it in Xcode and the localhost key didn't get added under NSExceptionDomains. Ended up editing it in text editor and solved the wrong key path.

That solved it! Thanks

I have followed integration-with-existing-apps guide and seeing this error. Added localhost as exception domain. My files are not in ios directory may this be an issue?

I did follow the integration-with-existing-apps, too. When I met this same issue, I just renamed my original folder which contains the iOS source code.
I ran this half an hour ago:
"mv originalFolderName ios" in the terminal before run "react-native run-ios", and it went well.

I have just started over, and it worked.

For me I just do a react-native upgrade then react-native run-ios and it works

I was having the following issue ENOENT: no such file or directory, uv_chdir when i

run _react-native run-ios_
my error gone when i run

react-native upgrade
and then

react-native run-ios

same problem here. any process?

@tewodroswondimu Your solution works very well. Thank you!!

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions.

I solved my problem by deleting the contents of the directory "C:\Users\JoaoHuss\AppData\Local\Temp\". A library that was added to a previous project with the same name, and this dependency of the library saved on that content of the temporary files.

I just restarted my system and it worked.

Was this page helpful?
0 / 5 - 0 ratings