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

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

About this issue

Original URL
State: closed
Created 8 years ago
Reactions: 9
Comments: 18 (2 by maintainers)

Commits related to this issue

fix: rn — committed to react-component/m-picker by paranoidjk 7 years ago

Most upvoted comments

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

+132

tewodroswondimu on Jun 15, 2017

experience similar issue

+36

gen4sp on Jan 4, 2017

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

+26

mrkem598 on Jul 6, 2017

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!

chuckhacker on Jan 12, 2017

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

temitope on Feb 21, 2017

same here

Update (2017-Feb-21)

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

1c7 on Feb 21, 2017

I have just started over, and it worked.

hovox on Mar 25, 2017

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

pbojinov on Feb 20, 2017

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.

jcollum on Jan 4, 2017

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.

xperiatrix on Mar 22, 2017