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.

debugger-ui not shown console.log

See original GitHub issue

In tab console shown this error and debugger-ui can’t see console to debug

debugger-ui:92 Uncaught TypeError: Cannot set property ‘volume’ of null at Object.render (debugger-ui:92) at Object.setState (debugger-ui:46) at WebSocket.ws.onopen (debugger-ui:150) render @ debugger-ui:92 setState @ debugger-ui:46 ws.onopen @ debugger-ui:150 debugger-ui:92 Uncaught TypeError: Cannot set property ‘volume’ of null at Object.render (debugger-ui:92) at Object.setState (debugger-ui:46) at WebSocket.ws.onclose (debugger-ui:187)`

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:23
  • Comments:21 (1 by maintainers)

github_iconTop GitHub Comments

48reactions
cadzcommented, Oct 22, 2017

ok, i think i finally able to get this to work. on the react-native app, press ctrl+M (or Command + M on mac, or “adb shell input keyevent 82” via shell) to open developer menu. and choose “Debug JS Remotely” . only after this the logging on debugger-ui will work.

you might want to close all opened debugger-ui windows/tabs. choosing debug js remotely will open a new tab.

22reactions
sinnercommented, Oct 19, 2017

I’m having the same problem. Moreover, this error is making me not able to print information to debug through the console.log method. Here more details about the error:

Uncaught TypeError: Cannot set property ‘volume’ of null at Object.render (debugger-ui:92) 92: silence.volume = 0.1; at Object.setState (debugger-ui:46) at WebSocket.ws.onopen (debugger-ui:150) debugger-ui:1

Error in event handler for (unknown): TypeError: Cannot read property ‘userId’ of undefined at chrome-extension://lifbcibllhkdhoafpjfnlhfpfgnpldfl/contentscript.js:1:841

Read more comments on GitHub >

github_iconTop Results From Across the Web

Chrome: console.log, console.debug are not working
As of today, the UI of developer tools in Google chrome has changed where we select the log level of log statements being...
Read more >
React Native Debugger - Stop Using Console Logs - Tutorial
Open launch.json from the .vscode directory. If you don't have this file, do not worry. Open the VS Code command palette (shortcut by...
Read more >
react native console.log output not going to debug console
I am making a react native app and awhile back all of my console.log statements have stopped printing out in the Debugger console...
Read more >
8 Ways to Debug your React Native App with Expo - Medium
Use breakpoints and console.log s to quickly make sure a certain piece of state is holding the correct value. You can follow along...
Read more >
Debugging - React Native
Accessing console logs​ ... You may also access these through Debug → Open System Log... in the iOS Simulator or by running adb...
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