Unable to find debuggable browser tab - debugging

Question

I am working with a Blazor wasm project. I have been trying to start the debugger browser dev tools with blazor and i keep getting an error
I hit
Debugging hotkey: Shift+Alt+D (when application has focus)
Which gives me
Unable to find debuggable browser tab
Could not get a list of browser tabs from http://localhost:9222/json. Ensure Chrome is running with debugging enabled.
Resolution
Close all Chrome instances, then press Win+R and enter the following:
"%programfiles(x86)%\Google\Chrome\Application\chrome.exe" --remote-debugging-port=9222 http://localhost:52878/
... then use that new tab for debugging.
Underlying exception: System.Net.Http.HttpRequestException: No
connection could be made because the target machine actively refused
it. ---> System.Net.Sockets.SocketException (10061): No connection
could be made because the target machine actively refused it. at
System.Net.Http.ConnectHelper.ConnectAsync(String host, Int32 port,
CancellationToken cancellationToken) --- End of inner exception
stack trace --- at
System.Net.Http.ConnectHelper.ConnectAsync(String host, Int32 port,
CancellationToken cancellationToken) at
System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage
request, Boolean allowHttp2, CancellationToken cancellationToken)
at
System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage
request, CancellationToken cancellationToken) at
System.Net.Http.HttpConnectionPool.GetHttpConnectionAsync(HttpRequestMessage
request, CancellationToken cancellationToken) at
System.Net.Http.HttpConnectionPool.SendWithRetryAsync(HttpRequestMessage
request, Boolean doRequestAuth, CancellationToken cancellationToken)
at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage
request, CancellationToken cancellationToken) at
System.Net.Http.DiagnosticsHandler.SendAsync(HttpRequestMessage
request, CancellationToken cancellationToken) at
System.Net.Http.HttpClient.FinishSendAsyncUnbuffered(Task1 sendTask,
HttpRequestMessage request, CancellationTokenSource cts, Boolean
disposeCts) at System.Net.Http.HttpClient.GetStringAsyncCore(Task1
getTask) at
Microsoft.AspNetCore.Builder.BlazorMonoDebugProxyAppBuilderExtensions.GetOpenedBrowserTabs(String
debuggerHost) at
Microsoft.AspNetCore.Builder.BlazorMonoDebugProxyAppBuilderExtensions.DebugHome(HttpContext
context)
I shut down all chome browser and run the command instructed but it doesnt help i get the same error
I suspect the issue is related to the fact that as soon as chrome starts it spawns a large number of other chromes i can see them
I tried killing them all so there was no chrome running then firing off the command that didnt work either because again i ended up with like 10 chromes running.
How do you find the debugged browser tab with blazor?

Answer 1

I am using Blazor webassembly, .NET Core 5.0.100-preview.7.20366.6 ; Google Chrome version 84.0.4147.105 (Official Build) (64-bit); Visual Studio 2019 preview Community edition.
You will see message like this
Unable to find debuggable browser tab
Could not get a list of browser tabs from http://127.0.0.1:9222/json. Ensure your browser is running with debugging enabled.
Resolution
If you are using Google Chrome for your development, follow these instructions:
Press Win+R and enter the following:
chrome --remote-debugging-port=9222 --user-data-dir="C:\Users\donhuvy\AppData\Local\Temp\blazor-chrome-debug" https://localhost:44376/
If you are using Microsoft Edge (80+) for your development, follow these instructions:
Press Win+R and enter the following:
msedge --remote-debugging-port=9222 --user-data-dir="C:\Users\donhuvy\AppData\Local\Temp\blazor-edge-debug" --no-first-run https://localhost:44376/
This should launch a new browser window with debugging enabled..
Let's do like the guide.
(1) Copy these text
chrome --remote-debugging-port=9222 --user-data-dir="C:\Users\donhuvy\AppData\Local\Temp\blazor-chrome-debug" https://localhost:44376/
(2) Press Windows+R, paste by Ctrl+V , then, press Enter
(3) Go to http://127.0.0.1:9222/json , you will see
this is debug information.
(4) When you press Shift+Alt+D