-
Notifications
You must be signed in to change notification settings - Fork 280
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
Exclude fragments from urlFilter matching #869
Comments
Can you try with the nightly build? I think the changes in #834 should fix this. In 1.50 (or maybe 1.49, I forget) we briefly introduced a change that made this work, but rolled it back with https://github.com/microsoft/vscode-chrome-debug/issues/719#issuecomment-705072583; the fix in 834 is the correct solution. |
Actually, I think it will still not work. Basically you want the url to actually be exactly |
@connor4312 , specifying "url" exactly as in browser made it work. In my case it was |
Actually I realized I already fixed this in #840. It's been released as of VS Code 1.52. |
Attach to chrome with remote debug fails without any error message since code 1.51.1. In 1.50 all worked fine.
Chrome version is latest 57.0.4280.66, started with
--remote-debugging-port=9222
and inspector is available from other chrome on http://localhost:9222/To Reproduce
--remote-debugging-port=9222
in 1.50 debugger toolbar appears and "Call stack" is populated with available pages,
in 1.51.1 debugger toolbar appears without "disconnect" button, and nothing in "Call Stack"
Log File
launch.json and debugadapter.json
VS Code Version: 1.51.1
Additional context
"Launch in chrome" still works perfectly.
The text was updated successfully, but these errors were encountered: