-
Notifications
You must be signed in to change notification settings - Fork 311
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Packager crashes, unable to talk to watchman #36
Comments
One solution that worked for me was after you quit Deco, go into Activity Monitor and kill any However, sometimes there is no watchman process there and I found I was still getting this error. However, I use tmux. I found that if I tried to start the packager manually "outside" of tmux (it might take a couple tries), it would end up working. Then trying back "inside" of tmux worked. Kinda strange, but I was able to reproduce this process reliably. |
I found the "tmux" solution on this issue: facebook/watchman#69 |
Yep, I was able to reproduce the same process, and also it's not possible to kill |
please reopen a separate issue if the error continues to persist. |
After i clicked one simulator, red box appeared in simulator which shows "could not connect to development server". Bellow are console error info in packager output:
┌────────────────────────────────────────────────────────────────────────────┐
│ Running packager on port 8081. │
│ │
│ Keep this packager running while developing on any JS projects. Feel │
│ free to close this tab and run your own packager instance if you │
│ prefer. │
│ │
│ https://github.com/facebook/react-native │
│ │
└────────────────────────────────────────────────────────────────────────────┘
Looking for JS files in
/Users/lizenghui/.Deco/tmp/Project
[11:25:02 AM] Building Dependency Graph
[11:25:02 AM] Crawling File System
[Hot Module Replacement] Server listening on /hot
React packager ready.
2016-05-27T11:25:02,749: [cli] failed to identify PDU: fill_buffer: EOF
2016-05-27T11:25:02,749: [cli] unable to talk to your watchman on /usr/local/var/run/watchman/lizenghui-state/sock! (Undefined error: 0)
/Users/lizenghui/Library/LaunchAgents/com.github.facebook.watchman.plist: service already loaded
2016-05-27T11:25:02,748: [cli] failed to identify PDU: fill_buffer: EOF
2016-05-27T11:25:02,749: [cli] unable to talk to your watchman on /usr/local/var/run/watchman/lizenghui-state/sock! (Undefined error: 0)
Watchman: watchman--no-pretty get-sockname returned with exit code 1 /Users/lizenghui/Library/LaunchAgents/com.github.facebook.watchman.plist: service already loaded
2016-05-27T11:25:02,748: [cli] failed to identify PDU: fill_buffer: EOF
2016-05-27T11:25:02,749: [cli] unable to talk to your watchman on /usr/local/var/run/watchman/lizenghui-state/sock! (Undefined error: 0)
ERROR watchman--no-pretty get-sockname returned with exit code 1 /Users/lizenghui/Library/LaunchAgents/com.github.facebook.watchman.plist: service already loaded
2016-05-27T11:25:02,748: [cli] failed to identify PDU: fill_buffer: EOF
2016-05-27T11:25:02,749: [cli] unable to talk to your watchman on /usr/local/var/run/watchman/lizenghui-state/sock! (Undefined error: 0)
Error: watchman--no-pretty get-sockname returned with exit code 1 /Users/lizenghui/Library/LaunchAgents/com.github.facebook.watchman.plist: service already loaded
2016-05-27T11:25:02,748: [cli] failed to identify PDU: fill_buffer: EOF
2016-05-27T11:25:02,749: [cli] unable to talk to your watchman on /usr/local/var/run/watchman/lizenghui-state/sock! (Undefined error: 0)
See http://facebook.github.io/react-native/docs/troubleshooting.html
for common problems and solutions.
Anyone come across this kind of situation?
The text was updated successfully, but these errors were encountered: