Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Basically...

My Blazor WASM app is stuck on mono_wasm_runtime_ready. The only way to progress is to open dev tools and resume, but this prevents breakpoints binding.

More Info

We have a corporate Blazor WASM app that we originally created in dotnet 5, which is now on dotnet 9.

It references the Framework JS file: _framework/blazor.webassembly.js.

When debugging it gets stuck in the mono_wasm_runtime_ready method on debugger;. I understand this is so VS can attach the debugger, but unfortunately it doesn't allow me to debug my app.

Some times, usually the first time in the day, it works fine: it goes to the home page and allows me to debug. But then after that it gets stuck.

My colleagues do not appear to have the issue, either.

The issue appears on both Edge and Chrome, with Extensions disabled.

What did I try?

1. Enabled Just My Code
2. Restart Visual Studio
3. Delete bin & obj folders => This seems to have helped, but then the issue reoccurs and I ain't doing this
4. Try moving everything to a brand new Blazor WASM app, but had a few issues (esp with auth) and spent too long on it

Not sure if it's related, but when stopping the debugging, the debugger doesn't close and I have to force it to.

Expected Behavior

It should navigate to the first page and breakpoints be bound.

Steps To Reproduce

Not sure, to be honest. Seems like it's environmental. Going to reclone it.

Exceptions (if any)

No Exceptions, just paused on debugger

.NET Version

dotnet 9

Anything else?

No response