WebSocket connection to 'ws://localhost:8081/debugger-proxy?role=debugger&name=Chrome' failed: Invalid frame header
Closed this issue · 46 comments
Seem to have started getting this random error when debugging with chrome, it will debug for a while and then die with the error:
WebSocket connection to 'ws://localhost:8081/debugger-proxy?role=debugger&name=Chrome' failed: Invalid frame header
We're using version 0.22 on the Mac with iOS
Also having this issue
+1
I restart my computer, and its gone.
Same. Version 0.22 on Mac with iOS.
so has this been fixed? I'm running http server in node, listening on port 3001 and after react-native recieves any error (like parse Error for example) I need to restart it and react-android app no longer connects to that node server. I end up with just that message in debugger:
"WebSocket connection to 'ws://localhost:8081/debugger-proxy?role=debugger&name=Chrome' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED"
I set up adb connection over wifi, 'adb devices' shows my phone and app starts normally - but doesnt connect over 3001
EDIT:
react-native-cli: 0.2.0
react-native 0.24.1
Also having same issue
try running 'adb reverse tcp:8081 tcp:8081' in terminal to access the development server from the device
Same issue here on 0.24 version for iOS
same issue, react native 0.26.3
I have the same issue when using Chrome, but it won't happen if I use https://github.com/jhen0409/react-native-debugger.
Experiencing the same issue with react-native: 0.28.0
EDIT: found a fix - https://medium.com/@davidguandev/lets-build-a-react-native-application-4190839a4f5c#.2jswlrano
@millerm are you referring to the ATS configuration in xcode ?
If so, it doesn't solve it for me. OSX / React native 0.28
Edit: --> I found a quick workarround that works for now by opening chrome in incognito mode
Perhaps it's antivirus? #7413
Have the same issue
RN 0.28
MAC OS
A colleague of mine had the same issue on node version 6.x. He downgraded to the same version I'm running, v5.9.1, and it resolved his issue.
Yup, I can confirm that Node 6.3 was the problem for me.
I downgraded as @hendrikswan suggested, but to version 6.2 and everything has been running without problems for a few hours.
Downgrading of Node from 6.3.0 to 6.2.2 didn't work for me;
Issue still persists.
Maybe downgrade further?
On Fri, 15 Jul 2016 at 08:47 Phillip Kingston notifications@github.com
wrote:
Downgrading of Node from 6.3.0 to 6.2.2 didn't work for me;
Issue still persists.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#6627 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAQsNZ1PwiqFnsXzGdPXWjsgYg-pg-w9ks5qVyz-gaJpZM4H4D2Z
.
I think this might be "fixed" in RN 0.30 which uses ws 1.1.1, which doesn't try to install native helper modules by default and should work more consistently across V8 versions.
Can someone confirm if RN 0.30 fixes this?
Have the same thing
I can confirm it is greatly improved in RN30. The error still pops up occasionally but its rare enough for it not to be a hindrance anymore.
RN 0.30.0 does appear to be much better, not getting the error on node 6.3.1. I was getting it with RN 0.29.0
Upgrading from 0.29.0 to 0.30.0 also seems to have fixed the issue for me.
same error with RN 0.27.2
Closing this issue since it's only happening with old versions AFAIK. Please open a new issue if the problem described in the first post is happening with RN 0.33+.
Similar error is preventing me from using Chrome dev tools for debugging React Native app.
WebSocket connection to 'ws://localhost:8081/debugger-proxy?role=debugger&name=Chrome' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
node v7.2.1
react-native-cli: 1.2.0
react-native: 0.44.0
Hello MarkPare,
I am having the same issue, inside react-native debugger console error follows: WebSocket connection to 'ws://localhost:8081/debugger-proxy?role=debugger&name=Chrome' failed: Error in connection establishment: net::ERR_CONNECTION_REFUSED
My Terminal is red and reads 'No Bundle URL Present'. Weird enough, my others aps I have made in the same folder don't have this issue.
react": "16.0.0-alpha.6",
"react-native": "^0.42.3",
"react-native-router-flux": "^3.39.1",
"react-redux": "^5.0.5"
Has anyone come across this recently?
Getting this on RN 0.45.1 :(
Same Issue RN 0.45.1
Same issue RN 0.47
Me too
+1 same error in debugger , getting hard day by day to use RN :(
Same issues
"react": "16.0.0-beta.5",
"react-native": "0.49.3",
"react-redux": "^5.0.6",
Having the same issue...
+1 => WebSocket connection to 'ws://localhost:19000/debugger-proxy?role=debugger&name=Chrome' failed: Connection closed before receiving a handshake response
Having the same issue...
"react": "16.0.0",
"react-native": "0.51.0",
having same issue.
"react": "^16.2.0",
"react-native": "^0.52.0".
Mac OS.
having same issue after update to:
"react": "^16.2.0",
"react-native": "0.52.1"
running android emulator
MacOS
having the same issue:
"react": "^16.3.0-alpha.1",
"react-native": "0.54.1",
iOS
When this happened to me I had the computer simulator and the device running at the same time. So it might have something to do with conflicting simulators
What fixed the issue for me => cleared my local cache using yarn clear cache then did a yarn install and ran the app again.
same issue
"react": "16.3.1",
"react-native": "0.55.4",
If you are using pusher server use cluster. I think error will be gone.
Any solution?
Having the same issue with RN 0.54.0