Hm, after a couple of retries and after waiting a huge amount of time, the project is finally created.

Hi @winterbe I had the same issue , I don't know why is it taking so long to init, what's the root cause?

I really don't know what causes this issue. It took like 10 min until some logs get printed and the command succeeded. Is there some kind of -verbose mode for react-native-cli? That would be handy in those situations.

Am 17.09.2015 um 17:28 schrieb Jr notifications@github.com:

Hi @winterbe I had the same issue , I don't know why is it taking so long to init, what's the root cause?

—
Reply to this email directly or view it on GitHub.

I get the same problem. I let it run for hours and it still hadn't gone beyond the one file and the same line mentioned above by @winterbe.

I am on node v4.0.0 and npm v2.14.2.

I first thought that it was a local problem on my machine/ network but it seems more and more people have the same problem.

So I reopen the issue now in hope that someone finds out the root cause of the problem.

+1

Happening for me too.

Same problem here, I have to keep trying to get it to complete and build.
Has anyone found a solution?

It's weird, it only happened to me on a MacBook where I had made some aborted early attempts to brew install, and hadn't done the updating and symlinking right and had to fix permissions prior to running the command line tool.

On my desktop Mac, when I brew updated first, it ran much smoother (and there weren't any symlink or permissions issues)

+1

Something is definitely taking too long, but it works after 10 minutes on my late 2012 macbook pro. I was about to give up but it kept spinning.

node --version
v4.1.1

It downloads about ~73mb of data and does that very slowly, but once it is downloaded, it goes through just fine. You can use something that monitors the git process to see where it's at.

I run --verbose, and it halts with this message:

npm WARN react-native@0.35.0 requires a peer of react@~15.3.1 but none was installed.
npm verb exit [ 0, true ]
npm info ok

How come it doesn't install this as supposed to?

Edit: this problem was solved by running @MichaelBurgess suggestion above :)

For reference @MichaelBurgess suggests doing this (should save you a click) and that suggestion worked for me

rm -rf /usr/local/var/run/watchman/ && brew uninstall watchman && brew install watchman

references

• http://stackoverflow.com/questions/39821692/react-native-init-hanging/39829694#39829694
• react-native init stuck #9943

@MichaelBurgess it helped, thanks

@MichaelBurgess i have same problem but on windows 8. any solution ? Thanks

react-native init <project> --verbose:
Verbose mode should maybe only display warnings and errors. It's incredibly cumbersome to scan through all those "verb" and "info" entries...

@captain-miao 厉害了，我的哥

I've this problem when try first run

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':app'.
> failed to find Build Tools revision 23.0.1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED
(node:4968) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): TypeError: Cannot read property 'message' of undefined
(node:4968) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Node: v7.2.1
npm: 4.0.5
Windows 10 Pro x64

It's weird, I had been facing this issue when I realized I was trying to init a project called test and there was already a test folder inside the directory.

@fourcolors This worked for me! Your awesome dude 👍 Spend a day and half trying to figure it out.

restarting multiple times got it to work for me.

@captain-miao soluation work for me, I am in China.

Will anyone tell how to fix this??