I'm using vscode. I cannot debug "standalone" (or "hosted") blazor wasm.
There are many questions like this, but they are for RCs, bugs apparently fixed for .NET 6, or tooling bugs apparently fixed in SDK 6.0.102.
I read all the docs. I suspect the problem is compounded by known hot reload compatibility bugs.
I am on the latest bits of everything. I'm using chromium on linux (ubuntu 20).
When I try debug, I get this error in a popup:
Unable to launch browser: "Failed to launch browser!
ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
WARNING: Kernel has no file descriptor comparison support: Operation not permitted
ERROR:process_singleton_posix.cc(341)] Failed to create /home/username/.config/Code/User/workspaceStorage/4208cd9cd69c4fe2a941aed538319caa/ms-vscode.js-debug/.profile/SingletonLock: Permission denied (13)
ERROR:chrome_browser_main.cc(1432)] Failed to create a ProcessSingleton for your profile directory. This means that running multiple instances would start multiple browser processes rather than opening a new window in the existing process. Aborting now to avoid profile corruption.
TROUBLESHOOTING: https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md
The error is not helpful, as I did chmod 777
for that directory, and yet it still complains about permissions. I also get other errors, also cryptic.
I'm wondering whether this is even possible, because after trawling dozens of SO questions and repo issues, I can't find anyone who claims to have a working setup and can show working config.
So: has anyone actually managed to get this working: blazor (standalone, but hosted is fine too), vscode, hot reload, linux? If you have, please post your working config?