"Socket hung up"
See original GitHub issueDependencies as follows.When debugger in browser, the result as follows. I don’t know weather the react-native of 0.42.0 result in this problem.
"dependencies": {
"antd-mobile": "^1.0.1",
"react": "~15.4.0",
"react-dom": "~15.4.0",
"react-native": "0.42.0",
"react-native-vector-icons": "^4.0.0",
"react-redux": "^5.0.3",
"react-web": "0.4.6",
"redux": "^3.6.0",
"redux-thunk": "^2.2.0"
},
"devDependencies": {
"babel-jest": "19.0.0",
"babel-loader": "^6.2.5",
"babel-plugin-import": "^1.1.1",
"babel-plugin-transform-runtime": "^6.23.0",
"babel-preset-react-native": "^1.9.0",
"babel-preset-stage-1": "^6.16.0",
"haste-resolver-webpack-plugin": "^0.2.2",
"jest": "19.0.2",
"json-loader": "^0.5.4",
"react-devtools": "^2.0.12",
"react-hot-loader": "^1.3.0",
"react-test-renderer": "~15.4.0",
"remote-redux-devtools": "0.5.0",
"remote-redux-devtools-on-debugger": "^0.7.0",
"webpack": "^1.13.2",
"webpack-dev-server": "^1.16.1",
"webpack-html-plugin": "^0.1.1"
},
Issue Analytics
- State:
- Created 7 years ago
- Reactions:4
- Comments:23 (9 by maintainers)
Top Results From Across the Web
NodeJS - What does "socket hang up" actually mean?
It means that socket does not send connection end event within the timeout period. If you are getting the request for cheerio via...
Read more >NodeJS - What does socket hang up actually mean - Edureka
When a socket hang up is thrown, one of two things happens: When you're a customer, When you send a request to a...
Read more >Could not get any response socket hang up - Help - Postman
I am not able to Post to the server. I am receiving “Could not get any response” error. While checking the logs found...
Read more >502 Bad Gateway - Socket hang up | Apigee Edge
The error code [socket hang up][ECONNRESET] indicates that the target server has closed the connection with Edge Microgateway. This can be ...
Read more >Hang in There! (A solution to socket hang up) - Medium
(A solution to socket hang up). Recently, while watching a YouTube video about how to create a Node.js backend (Building a RESTful API...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Using Expo, this only works 2/3 of the time, the other 1/3 I get this error. It sometimes goes away by just restarting, reloading or other ‘magic’ stuff, but I’d prefer to figure out how to get it working 3/3 times. Any steps I can take?
@marcusegues Have you reversed your ports using the ADB? (via running
adb reverse tcp:8000 tcp:8000
)That’s usually the most common reason for socket hung up - keep in mind that if you disconnect the device from your computer, the port doesn’t remain reversed; You have to (re-)run that ADB command every time you connect your device.