Create-react-native-app: node[6612] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)

[hengsoheak]

Description

Fresh install react native on MAC (MacBook Pro (Retina, 15-inch, Mid 2015) Version 10.12.5 (16F73)

Environment

Please run these commands in the project folder and fill in their results:

• npm ls react-native-scripts:
• npm ls react-native:
• npm ls expo:
• node -v:
• npm -v:
• yarn --version:
• watchman version:

Also specify:

1. Operating system:
   (MacBook Pro (Retina, 15-inch, Mid 2015)
2. Phone/emulator/simulator & version:
   Iphone 6 plush

Reproducible Demo

`npm WARN [email protected] requires a peer of react@>=15.4.0 but none was installed.
npm WARN [email protected] requires a peer of react@>=15.3.1 but none was installed.
npm WARN [email protected] requires a peer of react@>=15.4.0 but none was installed.

Success! Created AwesomeProject at /Users/sopheak/Documents/cam/react/AwesomeProject
Inside that directory, you can run several commands:

npm start
Starts the development server so you can open your app in the Expo
app on your phone.

npm run ios
(Mac only, requires Xcode)
Starts the development server and loads your app in an iOS simulator.

npm run android
(Requires Android build tools)
Starts the development server and loads your app on a connected Android
device or emulator.

npm test
Starts the test runner.

npm run eject
Removes this tool and copies build dependencies, configuration files
and scripts into the app directory. If you do this, you can’t go back!

We suggest that you begin by typing:

cd AwesomeProject
npm start

Happy hacking!
SOPHEAKs-MacBook-Pro:react sopheak$ cd AwesomeProject/
SOPHEAKs-MacBook-Pro:AwesomeProject sopheak$ npm test

[email protected] test /Users/sopheak/Documents/cam/react/AwesomeProject
node node_modules/jest/bin/jest.js --watch

2017-06-28 14:14 node[6612] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2017-06-28 14:14 node[6612] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2017-06-28 14:14 node[6612] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
events.js:160
throw er; // Unhandled 'error' event
^

Error: Error watching file for changes: EMFILE
at exports._errnoException (util.js:1018:11)
at FSEvent.FSWatcher._handle.onchange (fs.js:1420:11)
npm ERR! Test failed. See above for more details.
SOPHEAKs-MacBook-Pro:AwesomeProject sopheak$
`

[terribleben]

Hi, can you fill out the Environment part of the issue template so we know more about your system?

[andrewdelprete]

I'm also having this same issue. I received it after shelving a CRNA project for a few weeks and coming back to it and running yarn I believe. I've since deleted node_modules and tried again with the existing app but kept receiving the error @hengsoheak commented on. I tried uninstalling CRNA and reinstalling and starting a new project and got the same error.

[andrewdelprete]

➜  my-app npm ls react-native-scripts
[email protected] /Users/andrewdelprete/Work/my-app
├── UNMET PEER DEPENDENCY [email protected]
└── [email protected]

npm ERR! peer dep missing: react@>=15.4.0, required by [email protected]
➜  my-app npm ls react-native
[email protected] /Users/andrewdelprete/Work/my-app
├── UNMET PEER DEPENDENCY [email protected]
└── [email protected]

npm ERR! peer dep missing: react@>=15.4.0, required by [email protected]
➜  my-app npm ls expo
[email protected] /Users/andrewdelprete/Work/my-app
├─┬ [email protected]
│ └── UNMET PEER DEPENDENCY react@>=15.3.1
└── UNMET PEER DEPENDENCY [email protected]

npm ERR! peer dep missing: react@>=15.4.0, required by [email protected]
npm ERR! peer dep missing: react@>=15.3.1, required by [email protected]
npm ERR! peer dep missing: react@>=15.4.0, required by [email protected]
➜  my-app node -v
v7.7.1
➜  my-app npm -v
4.1.2
➜  my-app yarn --version
0.24.4
➜  my-app watchman version
Please specify a target and action

I tried brew uninstalling watchman and reinstalling but same issue. Possibly something to do with Watchman though?

[andrewdelprete]

Hey @hengsoheak, I was able to solve this issue. It had to do with the version of watchman I was running.

The steps I took:

1. npm uninstall watchman -g
2. brew install watchman
3. npm start from project directory

I had watchman installed globally with npm (wrong version maybe?). I uninstalled it and re-installed via brew and now it's working again. I hope this helps.

[hengsoheak]

Yes that it

[Luckvery]

I got this error, but then it went away when I bumped from jest version "jest": "20.0.4" to "jest": "23.2.0"