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.

Error activating auto attach, please report to https://aka.ms/js-dbg-issue

See original GitHub issue

✗ firebase emulators:start --inspect-functions
Debugger listening on ws://127.0.0.1:56849/df25ac21-1fd9-4af6-8c8b-281d113d9647
For help, see: https://nodejs.org/en/docs/inspector
Error activating auto attach, please report to https://aka.ms/js-dbg-issue
i  emulators: Starting emulators: functions, firestore, hosting
⚠  emulators: It seems that you are running multiple instances of the emulator suite for project [myproject]. This may result in unexpected behavior.
⚠  functions: You are running the functions emulator in debug mode (port=9229). This means that functions will execute in sequence rather than in parallel.
⚠  functions: The following emulators are not running, calls to these services from the Functions emulator will affect production: database, pubsub
⚠  Your requested "node" version "10" doesn't match your global version "14"
⚠  firestore: Did not find a Cloud Firestore rules file specified in a firebase.json config file.
⚠  firestore: The emulator will default to allowing all reads and writes. Learn more about this option: https://firebase.google.com/docs/emulator-suite/install_and_configure#security_rules_configuration.
i  firestore: Firestore Emulator logging to firestore-debug.log
i  hosting: Serving hosting files from: public
✔  hosting: Local server: http://localhost:5000
i  ui: Emulator UI logging to ui-debug.log
i  functions: Watching "/Users/fredriccliver/Projects/[myproject]/functions" for Cloud Functions...
>  Debugger listening on ws://localhost:9229/66cf42da-91f5-4f73-8a9e-69f13b83b215
>  Debugger listening on ws://localhost:9229/66cf42da-91f5-4f73-8a9e-69f13b83b215
>  Debugger listening on ws://localhost:9229/66cf42da-91f5-4f73-8a9e-69f13b83b215
>  For help, see: https://nodejs.org/en/docs/inspector
>  Error activating auto attach, please report to https://aka.ms/js-dbg-issue

My project is based on firebase and I’m using firebase emulator with --inspect-functions option. But, the remote debugging connection has been broken whenever I modified a functions-side(backend) code.

Issue Analytics

State:
Created 3 years ago
Comments:16 (8 by maintainers)

Top GitHub Comments

2reactions

fredricclivercommented, Oct 9, 2020

With the last VSCode delivery, this issue was totally resolved.

2reactions

connor4312commented, Sep 30, 2020

I fixed one case I happened to run into on OSX https://github.com/microsoft/vscode/commit/c17be0166314d1f83fd10eff380bfe36eca02e56

If this was the issue you were running into, it would also have ‘solved itself’ at some point when the OS cleared your temp directory.

Top Results From Across the Web

VSCode's Auto Attach is not toggling for Node.js

I use WSL to start VSCode with code . from my project directory in Windows Terminal. When VSCode starts up, "Auto Attach: Off"...

Debugger is unable to attach to chrome browser

Now when I run any debugging session I get the error attached. ... If we haven't resolved this issue for you, please report...

Troubleshooting and known issues (VS Tools for Unity)

Read about troubleshooting in Visual Studio Tools for Unity. See descriptions of known issues, and learn about solutions to those issues.

Debugging a Node.js app in VS Code - Section.io

You can look for an Auto Attach: On statement at the bottom blue bar in ... In the “Breakpoints” panel you can activate...

Firebase Functions debugging in Local VSCode. - Fredric Cliver

Fixing for problems. If your debug connection been broken, and you'd faced with this error. Error activating auto attach, please report to https:// ......