You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@varunajmera0 try killing the process of your browser and emulator. Run adb kill-server to remove your attached devices. Restart your emulator and rerun the remote debugger. The remote debugger should be pointing to your localhost:8081/debugger-ui
Reacted by Badr Aldeen Shek Salim, Nguyễn Trọng Vĩnh and Shaun Parkison
Reacted by Badr Aldeen Shek Salim and Shaun Parkison
I am using react native from past few months and never came across this error so why to kill the server, can you explain how it will help? How come this error came from nowhere I don't know. @blazergame
I had a similar issue last night. It seems like the emulator is connecting to an old debugger session. By resetting that connection, it'll create a new connection to reconnect with. If that didn't work, it might be something else that I'm not too sure of.
I have just deployed one app with "react-native": "0.52.2". It doesn't happen with this version ( "react-native": "0.52.2"). It is happening only with "react-native": "0.53.0".
It looks like your description is missing some necessary information, or the list of reproduction steps is not complete. Can you please add all the details specified in the template? This is necessary for people to be able to understand and reproduce the issue being reported.
I am going to close this, but feel free to open a new issue that meets the requirements set forth in the template. Thanks!
Reacted by parisaabasian, Sisir Das Kallil, Paulo Cabral Sanz and Adam Burdette
I have same issue with 0.54.
Why is react-native bridge asking Chrome to access http://10.0.2.2:8081/debugger-ui
?
this is an internal address within emulator and will not be accessible by chrome.
Not clear why this issue is closed, has it been resolved or is this a user error?
Reacted by Victor Malov, ShreyAhluwalia-HAI and Jesus Alvino
Press Cmd + M on emulator screen
Go to Dev settings > Debug server host & port for device
Set localhost:8081
Rerun the android app: react-native run-android
Debugger is connected now!
Reacted by Дмитрий, chenUT, Daniel Sánchez, Tim Scott, Moe Soheili, Masatsugu Omiya, pedrophilipecosta, hunginf, Satoshi Nitawaki, shukubota and 11 more
the perfect solution for this issue is:
Inside your emulator:
Press Cmd + M ( on Mac) or Ctrl+M ( on windows)
Go to Dev Settings and under Debugging menu click
Debug server host & port for device
Set it to localhost: 8081.
Reload the app.
Activity
react-native-bot commentedon Feb 8, 2018
@facebook-github-bot no-template
facebook-github-bot commentedon Feb 8, 2018
Something went wrong executing that command, @mkonicek could you take a look?
blazergame commentedon Feb 8, 2018
@varunajmera0 try killing the process of your browser and emulator. Run
adb kill-serverto remove your attached devices. Restart your emulator and rerun the remote debugger. The remote debugger should be pointing to yourlocalhost:8081/debugger-uivarunajmera0 commentedon Feb 8, 2018
I am using react native from past few months and never came across this error so why to kill the server, can you explain how it will help? How come this error came from nowhere I don't know. @blazergame
blazergame commentedon Feb 8, 2018
I had a similar issue last night. It seems like the emulator is connecting to an old debugger session. By resetting that connection, it'll create a new connection to reconnect with. If that didn't work, it might be something else that I'm not too sure of.
varunajmera0 commentedon Feb 9, 2018
I have just deployed one app with "react-native": "0.52.2". It doesn't happen with this version ( "react-native": "0.52.2"). It is happening only with "react-native": "0.53.0".
hramos commentedon Feb 9, 2018
Hey, thanks for reporting this issue!
It looks like your description is missing some necessary information, or the list of reproduction steps is not complete. Can you please add all the details specified in the template? This is necessary for people to be able to understand and reproduce the issue being reported.
I am going to close this, but feel free to open a new issue that meets the requirements set forth in the template. Thanks!
varunajmera0 commentedon Feb 10, 2018
What kind of description is missing or list of reproduction steps?
Your Dev tool is not launching.
varunajmera0 commentedon Feb 10, 2018
See again, every time I have to write manually this http://localhost:8081/debugger-ui/
vladp commentedon Apr 8, 2018
I have same issue with 0.54.
Why is react-native bridge asking Chrome to access http://10.0.2.2:8081/debugger-ui
?
this is an internal address within emulator and will not be accessible by chrome.
Not clear why this issue is closed, has it been resolved or is this a user error?
varunajmera0 commentedon Apr 9, 2018
@vladp they won't give any response. Before 0.54, I didn't get that error.
ichoubrahim commentedon Apr 24, 2018
Try to access the debugger with your local address : http://127.0.0.1:8081/debugger-ui/ or http://localhost:8081/debugger-ui/ because 10.0.x.x is not accessible by chrome.
alihalabyah commentedon May 4, 2018
Any updates on this?
devmrin commentedon May 17, 2018
Solved the issue for me following:
Press Cmd + M on emulator screen
Go to Dev settings > Debug server host & port for device
Set localhost:8081
Rerun the android app: react-native run-android
Debugger is connected now!
chenUT commentedon May 17, 2018
@devmrin 's solution works for me. Thanks.
YogendraShelke commentedon Jun 6, 2018
Use actual device for debugging
msoheilipro commentedon Jul 4, 2018
The solution by devmrin commented on May 17 works for me too
Johncy1997 commentedon Aug 27, 2018
@devmrin solution will work.
aswinaryal commentedon Sep 3, 2018
the perfect solution for this issue is:
Inside your emulator:
Press
Cmd + M( on Mac) orCtrl+M( on windows)Go to Dev Settings and under Debugging menu click