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

Debug JS Remotely crashes 0.52.0 #17941

Closed
Graham42 opened this issue Feb 12, 2018 · 15 comments
Closed

Debug JS Remotely crashes 0.52.0 #17941

Graham42 opened this issue Feb 12, 2018 · 15 comments
Labels
Ran Commands One of our bots successfully processed a command. Resolution: Locked This issue was locked by the bot.

Comments

@Graham42
Copy link

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 Ctrl+M to bring up the dev tools menu
  6. Select "Debug JS Remotely"
  7. In the Chrome browser that opens, open the web console Ctrl+Shift+I
  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 [email protected] installed

@KunwarSingh
Copy link

any updates on this issue, I'm facing this as well

@react-native-bot
Copy link
Collaborator

Thanks for posting this! It looks like you may not be using the latest version of React Native, v0.53.0, released on January 2018. Can you make sure this issue can still be reproduced in the latest version?

I am going to close this, but please feel free to open a new issue if you are able to confirm that this is still a problem in v0.53.0 or newer.

How to ContributeWhat to Expect from Maintainers

@react-native-bot react-native-bot added Ran Commands One of our bots successfully processed a command. Stale There has been a lack of activity on this issue and it may be closed soon. labels Feb 24, 2018
@stale stale bot removed the Stale There has been a lack of activity on this issue and it may be closed soon. label Feb 24, 2018
@Meligy
Copy link

Meligy commented Feb 25, 2018

I'm having the same issue with react-native [email protected]

Can we please reopen this issue?

@megelismi
Copy link

I'm also facing this issue with react-native [email protected]

@KunwarSingh
Copy link

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

@afilp
Copy link

afilp commented Feb 27, 2018

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.

@Pastromhaug
Copy link

Pastromhaug commented Feb 28, 2018

I'm having the same issue on 0.53.0 on Android

@afilp
Copy link

afilp commented Feb 28, 2018

Can this issue be reopened please? Why do bots close it?

It is obvious that when using Android Studio to "Debug app" then we get the Uncaught TypeError: Cannot set property 'volume' of null problem.

@jaredgalanis
Copy link

jaredgalanis commented Mar 2, 2018

For me adding export default to this line:

export default class App extends Component {

In App.js is what got rid of the issue.

@afilp
Copy link

afilp commented Mar 2, 2018

Thanks but I already have this export default in class.

@dhrubesh
Copy link

image
image
image

Can anyone help me on this?

@Graham42 Graham42 changed the title Debug JS Remotely crashes Debug JS Remotely crashes 0.52.0 Mar 17, 2018
@ldco2016
Copy link

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

Turning react extension off and on did not work.

Please help.

@speculees
Copy link

speculees commented Jun 10, 2018

Any updates on this?
{... "private": true, "devDependencies": { "babel-preset-react-native-stage-0": "^1.0.1", "jest": "^23.1.0", "jest-react-native": "^18.0.0", "react-test-renderer": "16.3.1" }, "scripts": { "start": "react-native start", "android": "react-native run-android", "ios": "react-native run-ios", "test": "jest" }, "jest": { "preset": "react-native" }, "dependencies": { "react": "16.3.1", "react-native": "~0.55.2", "react-native-maps": "^0.21.0" }... }

@Graham42
Copy link
Author

Graham42 commented Jun 11, 2018

React native folks generally don't check closed issues, @speculees ,recommend you open a new issue with the latest version

@iwenchao
Copy link

昨天我也遇到了这个问题,enable debug remotely crash. 不过我发现chrome 出现cached bundle. 所以清除了缓存.然后重新进入就好了 . 花了4个小时,有点心痛

@facebook facebook locked as resolved and limited conversation to collaborators Feb 24, 2019
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Feb 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Ran Commands One of our bots successfully processed a command. Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests