ignite: Info.plist: file does not exist or is not readable or is not a regular file
I’m getting the below error when I run “ignite new MyApp”
...
...
✔︎ Installing Ignite dependencies (~ 1 minute-ish)
✔︎ Linking external libs
⠋ Linking external libs./MyApp/ios/MyApp/Info.plist: file does not exist or is not readable or is not a regular file (Error Domain=NSCocoaErrorDomain Code=260 "The file “Info.plist” couldn’t be opened because there is no such file." UserInfo={NSFilePath=./MyApp/ios/MyApp/Info.plist, NSUnderlyingError=0x7fe499609ce0 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}})
✔︎ Updating PList file
⠋ Cleaning up after messy guestscd: no such file or directory: MyApp/android
/bin/sh: ./gradlew: No such file or directory
✔︎ Cleaning up after messy guests
Time to get cooking! 🍽
To run in iOS:
cd MyApp
react-native run-ios
To run in Android:
cd MyApp
react-native run-android
$ cd MyApp
$ react-native run-ios
ENOENT: no such file or directory, uv_chdir
$
Here’s the output of ignite doctor:
$ ignite doctor
Computer
Platform: darwin
Ignite
Version: 1.9.0
Path: /usr/local/bin/ignite
Node
Version: v6.6.0
Path: /usr/local/bin/node
NPM
Version: 3.10.3
Path: /usr/local/bin/npm
Yeoman
Version: 1.8.5
React Native CLI
Version: 1.0.0
App
React Native Version: ¯\_(ツ)_/¯
I can create “normal” React Native apps with react-native init MyApp
Am I missing something? I’m fairly new to Node and RN, although I have already been able to build part of my app from scratch and using existing libraries I have found in the web. This Ignite project though I’m starting it on a different folder, like, my existing partial app is under /dev/mobile/react and this Ignite app I’m trying to install and run under /dev/mobile/ignite
Any help will be greatly appreciated, looking forward to start using this amazing starter tool.
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 16 (7 by maintainers)
@GantMan it finally worked! I did npm update and I also installed yarn… I noticed this time it said something about using yarn or npm and it preferred yarn. I also noticed a warning about android SDK 23 not present, but it did work all the way this time!
Thanks for fixing this man, now time to enjoy and get started on a couple of apps I have in mind.
Cheers
Well, running the react-native init command with root seemed to work fine, so after a bit more of researching, I found this post with a lot of information about the problem: http://stackoverflow.com/questions/16151018/npm-throws-error-without-sudo/24404451#24404451
Then I ran this command: sudo rm -rf ~/.npm
Apparently, sometime when I was starting out with node I ran npm using sudo, and it might have broken something, and for some reason the permissions in that directory were still wrong even after trying reinstalling node or cleaning cache and what not.
Anyway, I still have the problem when running
ignite new appnamebut not when I runreact-native init appname --version0.34.1two times in a row with the same app nameI’m not sure if this “second run” fix would have worked or not without rf-ing my ~./npm directory
I will keep troubleshooting