question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cannot Use Remote Debugger

See original GitHub issue

Environment

React Native Environment Info: System: OS: macOS 10.14.1 CPU: (8) x64 Intel® Core™ 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: https://github.com/facebook/react-native/issues/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.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
matthargettcommented, Dec 10, 2018

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

1reaction
matthargettcommented, Nov 30, 2018

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.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Remote Debugging Errors and Troubleshooting
View links to common remote debugging errors in Visual Studio. Learn how to run the remote debugger as an administrator.
Read more >
Unable to connect with remote debugger - Stack Overflow
To solve the issue: Before enabling remote debugging on your emulator, open http://localhost:8081/debugger-ui in chrome. Then enable remote ...
Read more >
Not able to connect to VS 2019 remote debugger on Azure VM
The Visual Studio 2019 Remote Debugger (MSVSMON.EXE) does not appear to be running on the remote computer. This may be because a firewall...
Read more >
Remote Debugging with Visual Studio - IntervalZero
Remote Debugging with Visual Studio. This section describes the steps necessary for setting up a target PC and a host PC for debugging...
Read more >
Tutorial: Remote debug | IntelliJ IDEA Documentation - JetBrains
To allow the debugger to attach, we need to run the application with special parameters (more on them shortly). In this tutorial, we'll...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found