Wasm client using SignalR stopped working after update to .NET10

[emem67]

Current behavior 🐛

My webassembly clent uses SingalR for diplay some status it has stopped afer the framework update to version 10, if I buld and use the Desktop version it works I include a super small client server application that fails in my system
I tested this behaviour with 3 differnt versions of the UNO SDK

SignalR.zip

Expected behavior 🎯

The connection apparently works then SignalR events should be triggered in the client but they are not.

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

you can unzip the deno application build the server and run it. Build the client and run the Desktop version: it works, switch to webassembly it will not work.
If you can rebuild everithing going back to .NET9 you can see the webassembly version works.

Workaround 🛠️

Do not upgrade to .NET10 if you use webassembly and SignalR client

Renderer 🎨

• Skia
• Native

Affected platforms 📱💻🖥️

WebAssembly

Uno.Sdk version (and other relevant versions) 📦

Tested with 6.3.28, 6.4.24, 6.4.26 same result

IDE version 🧑‍💻

Visual studio 2026 18.0

Anything else we need to know? 💬

No response

[booskander]

browser console output when loading:

Could not load content for https://raw.githubusercontent.com/dotnet/runtime/b0f34d51fccc69fd334253924abd8d6853fad7aa/src/mono/browser/runtime/debug.ts (HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE)

It's likely a regression in .NET 10, gonna look for an open issue on their side ...

[booskander]

Similar issue seen here:

dotnet/runtime#121804

[booskander]

@kazo0 can confirm that it works fine with net9.0 but not with net10.0. Tested it with both VS 2022 and 2026 so I don't think the issue is related to the IDE. It seems like some files from dotnetruntime can't be fetched (invalid url) causing a silent exception. It might be linked to what @jeromelaban mentioned regarding AOT compiling for webassembly in .NET 10.