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 Use Remote Debugger #22368

Closed
jhwheeler opened this issue Nov 21, 2018 · 6 comments
Closed

Cannot Use Remote Debugger #22368

jhwheeler opened this issue Nov 21, 2018 · 6 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@jhwheeler
Copy link

Environment

React Native Environment Info:
System:
OS: macOS 10.14.1
CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Memory: 91.83 MB / 16.00 GB
Shell: 5.3 - /bin/zsh
Binaries:
Node: 10.6.0 - ~/.nvm/versions/node/v10.6.0/bin/node
Yarn: 1.12.3 - ~/.nvm/versions/node/v10.6.0/bin/yarn
npm: 6.4.1 - ~/.nvm/versions/node/v10.6.0/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
IDEs:
Android Studio: 3.1 AI-173.4819257
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
react: 16.5.0 => 16.5.0
react-native: https://github.com/expo/react-native/archive/sdk-31.0.1.tar.gz => 0.57.1

The app is using Expo v31.0.3 and expo-cli 2.4.0.

Description

The remote debugger does not work. The app works fine without the remote debugger active in both Android Emulator and iOS Simulator. Production mode is not active.

screenshot 2018-11-21 at 15 30 43

Here is the error message:

screenshot 2018-11-21 at 15 31 09

Changing the url to use localhost instead of the local IP does not fix it (as suggested in similar issue here: #17618. Furthermore we are not using xip.io).

Reproducible Demo

Not sure how to reproduce, as I can get the remote debugger working with a clean react-native init project. The repo is private, so I cannot share a link to it.

@radko93
Copy link
Contributor

radko93 commented Nov 21, 2018

I had a similar issue and I restarted simulator/packager/computer/browser and it was gone. DId you try it?

@jhwheeler
Copy link
Author

@radko93 Yes, I have. I've also tried removing and reinstalling node_modules, as well as removing the global expo-cli package.

This issue is being experienced by all 3 of the developers working on this app, and only appeared about a week or so ago.

@kelset
Copy link
Contributor

kelset commented Nov 22, 2018

I can get the remote debugger working with a clean react-native init project.

If this doesn't happen with react-native init it's probably related to:
a) something in your Metro configuration
b) something that is related to Expo

Either way I suggest you open an issue in one of those repositories.

@kelset kelset closed this as completed Nov 22, 2018
@matthargett
Copy link
Contributor

With newer Chrome and react-devtools, you have to use localhost (or the IP addresses involved have to be the same) in order to bypass CORS checking. This has come up quite a few times with teams I work with.

@kelset
Copy link
Contributor

kelset commented Dec 3, 2018

@matthargett do you want the issue to be reopened? Or there is some PR we can point people to?

@matthargett
Copy link
Contributor

no, just wanted to leave a workaround note for folks who end up here from a web search :)

@facebook facebook locked as resolved and limited conversation to collaborators Nov 22, 2019
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Nov 22, 2019
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

5 participants