We are hitting an infinite loop when trying to debug Blazor app from inside of codespaces.
Repro:
1) new codespaces (or WSL)
2) new blazor wasm app
3) run in debug
4) open the port with the app
5) shift+alt+d
6) instruction page appears: your browser does not run with debugging port opened
7) on the host machine: open the browser according to the instruction, with the debug port
8) shift+alt+d
9) expected: debugger gets attached, we are redirected to debugging dev tools
reality: instruction appears again: your browser does not run with debugging port opened.
Tagging subscribers to this area: @thaystg
See info in area-owners.md if you want to be subscribed.
Issue Details
We are hitting an infinite loop when trying to debug Blazor app from inside of codespaces.
Repro:
1) new codespaces (or WSL)
2) new blazor wasm app
3) run in debug
4) open the port with the app
5) shift+alt+d
6) instruction page appears: your browser does not run with debugging port opened
7) on the host machine: open the browser according to the instruction, with the debug port
8) shift+alt+d
9) expected: debuger gets attached, we are redirected to debugging dev tools
reality: instruction appears again: your browser does not run with debugging port opened.
We are hitting an infinite loop when trying to debug Blazor app from inside of codespaces. Repro: 1) new codespaces (or WSL) 2) new blazor wasm app 3) run in debug 4) open the port with the app 5) shift+alt+d 6) instruction page appears: your browser does not run with debugging port opened 7) on the host machine: open the browser according to the instruction, with the debug port 8) shift+alt+d 9) expected: debugger gets attached, we are redirected to debugging dev tools reality: instruction appears again: your browser does not run with debugging port opened.