Skip to content
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

Cannot connect to remote debugger when using android real device with charlse proxy enabled. #14758

Closed
Obooman opened this issue Jun 28, 2017 · 8 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@Obooman
Copy link

Obooman commented Jun 28, 2017

Is this a bug report?

Yes,I think it's a bug with react-native itself.

Have you read the Bugs section of the Contributing to React Native Guide?

Yes,the bug can only be reproduced with real devices.

Environment

  1. react-native -v:0.45.1
  2. node -v:v7.8.0
  3. npm -v:5.0.3
  4. yarn --version:0.15.1

Then, specify:

  1. Target Platform (e.g. iOS, Android):Android
  2. Development Operating System:macOS Sierra 10.12.5 (16F73)
  3. Build tools : Android Studio 2.2.2 , SDK 21

Steps to Reproduce

1.With a local node data server running,hijacked http://demo.com:6003 to local server with hosts.
2.open Charlse as device proxy set my android phone proxy to Charlse address
3.Shake the phone and press debug Debug JS Remotely,react native package process log Launching Dev Tools... and http://localhost:8081/debugger-ui shown,but android device keeps showing connecting to remote debugger green bar and after short time it shows Timeout while connecting to remove debugger

Expected Behavior

I can connect to remote debugger successfully,log my http response from server .

Actual Behavior

packager server acts but real device cannot aware of conneted info.
PS:the packager works well and if I do not open Debus js remotely everything works well,the aoo compile and reload well.

Reproducible Demo

Real Device bug,there's no demo can be offered.
have changed ip address to IP or localhost,no difference.

@th317erd
Copy link

Same issue for me

@Obooman
Copy link
Author

Obooman commented Jul 10, 2017

As there's no one reply the issue I'll close it.But I have to say the problem still exits.
😞
By moving website to a public repo and chrome devTool network panel,I can continue my development

@Obooman Obooman closed this as completed Jul 10, 2017
@pangpond
Copy link

pangpond commented Dec 3, 2017

I resolve this by disable production config in main App

// console.disableYellowBox = true
// console.error = error => error.apply
// NativeModules.ExceptionsManager = null

@rutsatz
Copy link

rutsatz commented Feb 13, 2018

For me, it solved to uninstall the app in the real android device and install it again by running react-native run-android in the terminal. After that, shake the device and enable debugger. Everything works.

@hjJunior
Copy link

I got the same problem using react native 0.53

@iastanley
Copy link

I also have the same issue using react native 0.53 on macOS with android virtual device emulator. In addition when I try to enable debugging and it fails I am always taken to this url: http://10.0.2.2:8081/debugger-ui. When it works I am redirected to this url: http://localhost:8081/debugger-ui/

I have only gotten the debugger to work once out of over a dozen times restarting terminal instance, browser, emulator etc. trying to get it to work.

@nhuthuynh
Copy link

same here, I am using react-native 0.5.3 running on mac os. Trying to reverse port in terminal but it does not help.

@nhuthuynh
Copy link

nhuthuynh commented Mar 10, 2018

Follow this stackoverflow question, the second answer works for me!

@facebook facebook locked as resolved and limited conversation to collaborators Jul 10, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

8 participants