[WASM] VS Code + WSL 2 Debug unbound breakpoint

[microhobby]

trafficstars

Current behavior

When trying to debug a WASM project using the VS Code WSL 2 remote connection it opens the browser chosen in the type seted on launch.json but does not stop at the set breakpoints:

Expected behavior

Breakpoints working

How to reproduce it (as minimally and precisely as possible)

• Use a WSL 2 Distro (I'm using Debian)
• Create a WASM unoapp using dotnet CLI with the -v flag to create the .vscode configuration
• Set a breakpoint
• Run the application
• Run the debugger

Workaround

Environment

Nuget Package: Uno.UI.WebAssembly 3.6.0-dev.336

• [x] Uno.UI / Uno.UI.WebAssembly / Uno.UI.Skia
• [ ] Uno.WinUI / Uno.WinUI.WebAssembly / Uno.WinUI.Skia
• [ ] Uno.SourceGenerationTasks
• [ ] Uno.UI.RemoteControl / Uno.WinUI.RemoteControl
• [x] Other: VS Code WASM debugger on WSL 2

Nuget Package Version(s):

Affected platform(s):

• [ ] iOS
• [ ] Android
• [x] WebAssembly
• [ ] WebAssembly renderers for Xamarin.Forms
• [ ] macOS
• [ ] Skia
  • [ ] WPF
  • [ ] GTK (Linux)
  • [ ] Tizen
• [ ] Windows
• [ ] Build tasks
• [ ] Solution Templates

IDE:

• [ ] Visual Studio 2017 (version: )
• [ ] Visual Studio 2019 (version: )
• [ ] Visual Studio for Mac (version: )
• [ ] Rider Windows (version: )
• [ ] Rider macOS (version: )
• [x] Visual Studio Code (version: 1.55.0-insiders)

Relevant plugins:

• [ ] Resharper (version: )

Anything else we need to know?

[lukeblevins]

I can reproduce this WASM debugging issue on macOS as well when using VS Code.

[jeromelaban]

This is a scenario that is not yet supported by VS Code, even in "standard" Javascript debugging.