react-native: Debug JS Remotely crashes 0.52.0

Is this a bug report?

Yes

Have you read the Contributing Guidelines?

Partly

Environment

Environment: OS: Linux 4.4 Node: 8.9.4 Yarn: 1.3.2 npm: 5.6.0 Watchman: Not Found Xcode: N/A Android Studio: 3.0 AI-171.4443003

Packages: (wanted => installed) react: 16.2.0 => 16.2.0 react-native: 0.52.0 => 0.52.0

Steps to Reproduce

  1. Create a project following the Getting Started guide (Quick start tab)
  2. Switch to the Building Projects with Native Code tab of the guide, and follow the steps there to create an Android Virtual Device
  3. Start the Android Virtual Device
  4. Run npm run android in the fresh project
  5. Once the app has loaded in the Android emulator, press <kbd>Ctrl+M</kbd> to bring up the dev tools menu
  6. Select “Debug JS Remotely”
  7. In the Chrome browser that opens, open the web console <kbd>Ctrl+Shift+I</kbd>
  8. Enable Pause on exceptions
  9. Reload the Chrome page
  10. Error will occur here

Expected Behavior

The debugger to not crash

Actual Behavior

The debugger crashed.

Stacktrace:

(index):94 Uncaught TypeError: Cannot set property 'volume' of null
    at Object.render ((index):94)
    at Object.setState ((index):48)
    at WebSocket.ws.onopen ((index):152)

image

Reproducible Demo

No project code changes are need to reproduce this. Just run

npx create-react-native-app TestProject

Note: npx is available if you have the at least npm@5.2.0 installed

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 9
  • Comments: 15

Most upvoted comments

Its working now on 0.53.0 Just turn off all your google chrome extensions and restart it. Then debug-mode works like charm.

I am also getting this issue in the http://localhost:8081/debugger-ui/.

Turning react extension off and on did not work.

Please help.

image image image

Can anyone help me on this?

I am also having the issue in 0.53.0. Sometimes it works sometimes not. Disabling all extensions should not be the solution (not even tried this), because we will not be able to work on chrome with many other websites during development.