-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Description
Is there an existing issue for this?
- I have searched the existing issues
Describe the bug
A published Blazor WebAssembly application doesn't work.
The mono wasm runtime encounters an error and the application simply halts.
Expected Behavior
I expect the Blazor Web App template to run when published. Even without any modification it doesn't work.
Steps To Reproduce
- Create a new "Blazor Web App" (.NET 9 WebAssembly) (Also happend for .NET 10 Preview)
- Publish to a folder (All default settings)
- Run the exe file and open the website in a Browser (Tested with Edge or Firefox)
The issue can be "fixed" by add this to the client project:
<WasmFingerprintAssets>false</WasmFingerprintAssets>
This will however make the published WASM much larger and doesn't seem like a good solution.
In any case the default Blazor Web App should work without such modification.
Exceptions (if any)
[MONO] * Assertion at /__w/1/s/src/mono/mono/metadata/assembly.c:2718, condition `' not met
Fc<@http://localhost:5000/_framework/dotnet.runtime.drv0pr9n5o.js:3:168833
@:wasm-function[158]:0xac91
@:wasm-function[649]:0x43052
@:wasm-function[567]:0x4105b
@:wasm-function[571]:0x4117c
@:wasm-function[573]:0x411bf
@:wasm-function[572]:0x41192
@:wasm-function[157]:0x8cf4
createDotnetRuntime/Module._mono_wasm_load_runtime@http://localhost:5000/_framework/dotnet.native.l4ptthxatg.js:8:114094
Wc/e.onRuntimeInitialized/<@http://localhost:5000/_framework/dotnet.runtime.drv0pr9n5o.js:3:184839
Wc/e.onRuntimeInitialized/<@http://localhost:5000/_framework/dotnet.runtime.drv0pr9n5o.js:3:184967
Wc/e.onRuntimeInitialized/<@http://localhost:5000/_framework/dotnet.runtime.drv0pr9n5o.js:3:188548
.NET Version
10.0.100-rc.2.25502.107 (but the project is .NET 9)
Anything else?
Visual Studio Insiders [11123.170]