-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
Debug blazor in vscode prompted "cannot launch browser: The URL's protocol must be one of "ws","wss:, or "ws+nuix;""" #45257
Comments
@LZD121 thanks for contacting us. @TanayParikh can you take a look at this? |
To learn more about what this message means, what to expect next, and how this issue will be handled you can read our Triage Process document. |
I have the same problem since time ago. I assumed it was a local problem. In VS2022 everything works fine. In VSCODE the debug does not work well. I had the problem with .NET6, I upgraded to .NET7 and the problem is still the same. With edge there is no difference. While I wait for a solution I debug with the chrome developer tools. It more or less meets my needs, at moment. Thanks @LZD121 ! |
You'll need to add the Marking this as resolved. Please let us know if you're still experiencing this issue after following the guidance in the documentation above. |
Hi, @TanayParikh thanks. I have followed all the steps of the documentation but it does not solve the problem. I do the tests by creating a clean project. |
More info, With Microsoft.AspNetCore.Razor.VSCode.BlazorWasmDebuggingExtension v1.1.0 and v1.0.1 the same error happens. But, with Microsoft.AspNetCore.Razor.VSCode.BlazorWasmDebuggingExtension v1.0.0 apparently it launches the browser fine, and the debug proxy connects. |
cc/ @thaystg in case you have context on this issue |
Yes, this is fixed in this PR: dotnet/razor#7929 |
Thanks @thaystg |
This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes. See our Issue Management Policies for more information. |
I don't believe this issue is resolved because I am experiencing it now in VSCode using the blazorwasm template with no modifications. I get the same "Unable to launch browser" issue. |
The issue has been resolved via the PR mentioned above. The code hasn't yet shipped so you'll still be seeing the older behavior for now. |
I have the same issue.
When will be the fix shipped? |
My launch.json:
The chrome is opened, but displays blank page.
The text was updated successfully, but these errors were encountered: