Closed
Labels
Resolution: LockedThis issue was locked by the bot.This issue was locked by the bot.
Description
just upgraded to Sierra and am running into a problem when i enter NPM start
For background, I am on react-native 0.26 and unfortunately cannot upgrade at the moment. I also do not have brew
My logs show the following when I try NPM start:
2016-09-21 12:35 node[1515] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2016-09-21 12:35 node[1515] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2016-09-21 12:35 node[1515] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2016-09-21 12:35 node[1515] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2016-09-21 12:35 node[1515] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2016-09-21 12:35 node[1515] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2016-09-21 12:35 node[1515] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2016-09-21 12:35 node[1515] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2016-09-21 12:35 node[1515] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2016-09-21 12:35 node[1515] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2016-09-21 12:35 node[1515] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2016-09-21 12:35 node[1515] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
ERROR Error watching file for changes: EMFILE
{"code":"EMFILE","errno":"EMFILE","syscall":"Error watching file for changes:","filename":null}
Error: Error watching file for changes: EMFILE
at exports._errnoException (util.js:953:11)
at FSEvent.FSWatcher._handle.onchange (fs.js:1400:11)
Reacted by Joshua Pinter, FilipLukac, Copypeng, Khalid1201, Initial M, Supriya Kalghatgi, Arwiz, kiranraj2k, David C, Per Lundberg and 26 more
Metadata
Metadata
Assignees
Labels
Resolution: LockedThis issue was locked by the bot.This issue was locked by the bot.
Activity
AlexisLeon commentedon Sep 21, 2016
I have the same error.
I just upgraded to macOS Sierra too
Etheryte commentedon Sep 21, 2016
Have you checked the solutions in #9309?
mrkhan2 commentedon Sep 21, 2016
@Etheryte yes checked it out. Seems to only be a solution for those with brew/watchman installed.
leecade commentedon Sep 22, 2016
resolved via: leecade/react-native-practice#21
oscardemoya commentedon Sep 22, 2016
I was checking watchman issues and found out this one: meta/watchman#358
When running
watchman watch-listI got some permissions error.chmod 0700 /usr/local/var/run/watchman/<USER>-stateworked for me.AlexisLeon commentedon Sep 24, 2016
The problem can be solved by reinstalling react-native-cli:
raichur commentedon Sep 24, 2016
@AlexisLeon that didn't work for me.
Luavis commentedon Sep 27, 2016
This answer(#9309) work to me. I create and eidt new
sysctl.confand install watchman through homebrew.1. increase max file limt
2. upgrade to watchman 4.6
gnestor commentedon Sep 27, 2016
I'd like to add that I've been running the packager without watchman for 3-4 months because React Native's Node packager doesn't depend on watchman. However, after upgrading to macOS Sierra the Node packager started failing with the above errors. Installing the current version of watchman (
brew install watchman) did solve the issue for me, but something obviously regressed and it would be good to understand what that is.bbb324 commentedon Sep 30, 2016
@Luavis still didn't work, when I execute ./autogen.sh
Luavis commentedon Oct 2, 2016
@bbb324 Could you try install watchman by homebrew
sanqianpiao commentedon Oct 28, 2016
Thanks to @Luavis , I followed his steps, still resulted in failure.
In my case, need another operation that mentioned below:
#910 (comment)
mikeyang01 commentedon Nov 7, 2016
I reinstall node, watchman, npm and etc, finally everything goes fine!
I think new updates about supporting mac OS Sierra were included in the package.
brew install nodebrew install watchmanbrew link automake pcrenpm install -g react-native-cliexport ANDROID_HOME=~/Library/Android/sdkexport PATH=${PATH}:${ANDROID_HOME}react-native run-androidankitduseja commentedon Nov 11, 2016
brew install watchmansolved it for me but had to update xcode to 8.1 also in order to install watchman.4 remaining items
mg commentedon Dec 17, 2016
If you are still getting this error and are using tmux on MacOS Sierra, try open a new terminal without tmux and run 'watchman version'. After doing that, it was fixed for me within tmux.
levarberry commentedon Feb 26, 2017
Installing watchman worked for me.
manuelprojects commentedon May 6, 2017
Same, installed watchman fixed the issue
manbearshark commentedon Jun 29, 2017
This just happened to me after transferring my environment from an old MacBook Pro to a brand new one.
Using Watchman 4.7.0 and brew - problem seems to be a permissions issue with the watchman state directory, so running:
chmod 0700 /usr/local/var/run/watchman/<YOUR USERNAME HERE>-statedid the job.
sandip7484 commentedon Aug 21, 2017
@Luavis i install watchman by homebrew thanks!!
AnshuGoyal commentedon Sep 5, 2017
Clearing the builds in android->app->build folder and hitting react-native run-android worked for me.
johnwangel commentedon Oct 10, 2017
Hello. I have tried everything listed above, but I continue to get this error: node[10626] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
I just upgraded to High Sierra. I had deleted XCode and Android Studio, and then reinstalled both.
I've installed watchman 4.9.0 (and also uninstalled) - no help.
I've increased the max file limit - no help.
I've reinstalled react-native and npm - no help.
Any other ideas what I can do.
Thank you,
John
viatsko commentedon Oct 10, 2017
This is a correct way of increasing limit on max files for Mac OS X Sierra and above https://superuser.com/a/1171028, works for me on a huge repo w/o any issues (and doesn't in case of default limits)
viatsko commentedon Oct 10, 2017
Actually, what if react-native/nuclide will provide instructions on how to raise limit instead of throwing an error?
prancky commentedon Oct 14, 2017
@johnwangel this will help you to fix that error https://facebook.github.io/watchman/docs/install.html
johnwangel commentedon Oct 14, 2017
Thank you @pranky. I tried reinstalling watchman and just about everything else I could think of, to no avail. The thing that worked was to create a new project and port the code into that project - so I guess there was something cached in the old project that I wasn't able to find.
Premjeet-Singh commentedon Dec 7, 2017
brew install watchmanworked for me.gramster commentedon Feb 17, 2018
Increasing file limits, installing watchman and reinstalling react-native-cli did not fix this for me. Why is this issue closed?