Try this configuration in your launch file:

{
    "name": "Attach to Process",
    "type": "node",
    "protocol": "inspector",
    "request": "attach",
    "stopOnEntry": false,
    "port": 5858,
    "localRoot": "${workspaceRoot}",
    "remoteRoot": "/somepath/myprojectroot",
    "sourceMaps": true
}

Make sure the remoteRoot is correct path, otherwise it won't know where to look for the source files.

Answer from alkasai on Stack Overflow
🌐
GitHub
github.com › microsoft › vscode-react-native › issues › 625
Breakpoint set but not yet bound · Issue #625 · microsoft/vscode-react-native
February 5, 2018 - Actual Behavior Breakpoint does not stop code execution Expected Behavior Breakpoint stops code execution Latest version of everything. "Breakpoint set but not yet bound" is displayed when hovering over the breakpoint. Debugger is workin...
Author   dancomanlive
🌐
GitHub
github.com › Microsoft › vscode › issues › 51683
Unverified breakpoint, Breakpoints set but not yet bound <Node.js> · Issue #51683 · microsoft/vscode
June 12, 2018 - I'm trying to debug a Node.js application using the 'Debugger for chrome' extension. Expected behaviour stop the program when it reaches any breakpoint. Actual behaviour does not stop at any breakpoint. the black breakpoint (not a regula...
Author   reverietito
🌐
GitHub
github.com › Microsoft › vscode › issues › 62364
Breakpoint set but not yet bound · Issue #62364 · microsoft/vscode
November 1, 2018 - VSCode Version: 1.28.2 OS Version: 10.13.5 Steps to Reproduce: 1.add the breakpoint in the file 2.when debuging, the breakpoint turns gray and unverified breakpoint 3.when set trace verbose in laun...
Author   huyaweii
🌐
Wordpress
ianvink.wordpress.com › 2020 › 03 › 09 › vscode-handling-debugging-error-breakpoint-set-but-not-yet-bound
#VSCode: Handling Debugging Error “Breakpoint set but not yet bound” | Asp.Net Core, Angular, Xamarin and Maui
August 15, 2020 - Tip: When you open the folder in VS Code, do so at the root where the .vscode folder is. The e2e, src etc folders should all be at the top level. ... It’s all about in what folder you opened your workspace in. This affects “webRoot”: “${workspaceFolder}/MAYBE-THIS-my-app/” · I’ve noticed that sometimes you still get the error “Breakpoint set but not yet bound” after the first try.
🌐
GitHub
github.com › microsoft › vscode › issues › 122580
Breakpoints not working - "Breakpoint set but not yet bound" · Issue #122580 · microsoft/vscode
April 28, 2021 - When it launches all of the break points change to "Breakpoint set but not yet bound"
Author   Rohit459
🌐
GitHub
github.com › Microsoft › vscode › issues › 60139
Breakpoint set but not yet bound (Issue #625) still exists · Issue #60139 · microsoft/vscode
October 8, 2018 - Issue Type: Bug VSCode version 1.27, and the breakpoint issue is not solved yet. I try to set breakpoints (clicking on the red dots), but when I run the debugger, it says "Breakpoints set but not yet bound". Same as issue #625: microsoft...
Author   rafaelbdb
Find elsewhere
🌐
GitHub
github.com › Microsoft › vscode-node-debug2 › issues › 177
Got "Breakpoint set but not yet bound" on debug start · Issue #177 · microsoft/vscode-node-debug2
March 12, 2018 - We are maintainers of vscode-react-native extension and recently we've got the following issue: microsoft/vscode-react-native#625 (comment) - for some reason, debugging does not stop on breakpoints on the first start, but it actually works as expected when we are removing and adding breakpoints again.
Author   ruslan-bikkinin
🌐
GitHub
github.com › Microsoft › vscode › issues › 40813
Debugging with ts-node in WSL: Breakpoints set but not yet bound · Issue #40813 · microsoft/vscode
December 25, 2017 - Any breakpoints in my .ts files are greyed out and have the tooltip "Breakpoints set but not yet bound".
Author   rhyek
🌐
Developer Community
developercommunity.visualstudio.com › content › problem › 935013 › breakpoints-set-but-not-yet-bound-268468-should-be.html
Developer Community
Skip to main content · Visual Studio · Guidelines Problems Suggestions Code of Conduct · Downloads · Visual Studio IDE Visual Studio Code Azure DevOps Team Foundation Server Accounts and Subscriptions · Subscriber Access · Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft ...
🌐
GitHub
github.com › Microsoft › vscode-chrome-debug-core › issues › 293
Got "Breakpoint set but not yet bound" on debug start · Issue #293 · microsoft/vscode-chrome-debug-core
February 26, 2018 - We are maintainers of vscode-react-native extension and recently we've got the following issue: microsoft/vscode-react-native#625 (comment) - for some reason, debugging does not stop on breakpoints on the first start, but it actually works as expected when we are removing and adding breakpoints again.
Author   sergey-akhalkov
🌐
GitHub
github.com › Microsoft › vscode-react-native › issues › 630
breakpoints set but not yet bound · Issue #630 · microsoft/vscode-react-native
February 16, 2018 - Actual Behavior program doesn't stop at any breakpoints Expected Behavior program should stop at breakpoints It used to work, now it doesn't work on any project now. It does stop on debugger expression in code though. Is something wrong ...
Author   novellizator
🌐
GitHub
github.com › Microsoft › vscode › issues › 48172
Breakpoint set but not yet bound · Issue #48172 · microsoft/vscode
April 19, 2018 - Issue Type: Bug Version of VS code is 1.22. When I am trying to debug the code, debug points turns into gray and debugging is not possible at the point. When hovering on gray debug point it shows tooltip error as "Brakpoint is not valid,...
Author   btushar
🌐
GitHub
github.com › microsoft › vscode-remote-release › issues › 2068
Breakpoint set but not yet bound in · Issue #2068 · microsoft/vscode-remote-release
December 20, 2019 - When trying to debug, it shows the message: Breakpoint set but not yet bound in · From the Debug Console, the .scripts command seems to return all the file · › http://localhost:3006/static/js/0.chunk.js (/__vscode-remote-uri__/workspaces/test_create_react_app/static/js/0.chunk.js) - ...
Published   Dec 20, 2019