Dev Tunnels not working with Blazor WebAssembly

[wicketbr]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

The Dev Tunnels feature only seems to work with Blazor Server apps. As soon as WebAssembly is used the Dev Tunnels fails to run.

Expected Behavior

I would expect that the application would start in a browser using the Dev Tunnels URL just like happens with other types of applications, including Blazor Server apps.

Steps To Reproduce

Create a new Blazor project using WebAssembly or Auto (Server and WebAssembly), enable a Dev Tunnel, and start debugging.

Exceptions (if any)

No response

.NET Version

8.0.100

Anything else?

[javiercn]

@wicketbr thanks for contacting us.

@danroth27 can you route this to the right folks?

[javiercn]

Actually, the issue seems to be coming from the debugger adapter

[javiercn]

@wicketbr I think you might need to add the NO_PROXY environment variable to your launchSettings.json file. The value needs to be localhost or 127.0.0.1

Let us know if this works for you.

Hi @wicketbr. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[wicketbr]

I added the NO_PROXY tag to my launchSettings.json file as:

"IIS Express": {
"commandName": "IISExpress",
"launchBrowser": true,
"environmentVariables": {
"ASPNETCORE_ENVIRONMENT": "Development",
"NO_PROXY": "localhost"
},
"inspectUri": "{wsProtocol}://{url.hostname}:{url.port}/_framework/debug/ws-proxy?browser={browserInspectUri}"
},

It didn't make any difference. I still got the same error message when trying to run the app with a Dev Tunnel active. I tried modifying the file in both the server hosting the WASM project and the client.

[danroth27]

@sayedihashimi Does this dev tunnels issue need to be submitted as a Visual Studio feedback ticket?

[mkArtakMSFT]

Ping @sayedihashimi, @vijayrkn

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.