microsoft / microsoft/vscode-azureresourcegroups
[CoR] Debug session fails with "Unable to attach to browser" after selecting Keep iterating
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 78
- Forks
- 55
- Avg merge
- 16h 49m
- Merged PRs (30d)
- 139
Description
OS: Win11 x64
VS Code Insider: 1.132.0-insider
Build Version: 0.12.7-alpha.0
Regression: Not a regression
Repro Steps:
- Create a project using Copilot
- In Development (Next steps)->select Keep iterating--start debugging and improve my code
- Press F5
- Wait for the application to launch
Expect:
The application launches and the debugging session starts without showing any error message
Actual:
Debug session fails with "Unable to attach to browser"
More Info:
After the error is shown, manually opening the local URL displays the application correctly.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure using the listed Copilot workflow on Windows 11 with the specified VS Code Insider build, then trace the extension's browser-attach flow reached by pressing F5. Compare the failed session with manually opening the local URL; done means the application launches, the debugger attaches, and no error is shown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100