rkttu
October 24, 2025, 11:21am
1
열림 08:25AM - 09 Oct 25 UTC
닫힘 11:58AM - 11 Oct 25 UTC
area-blazor
**REGRESSION INFO:** Works well on 10.0 RC 1 and Previous 10.0 RC 2 build
**I… NSTALL STEPS:**
1. Install Latest 10.0 RC 2 from Release Tracker
2. Apply Feed and do feed workaround
**Platform**
- [x] Windows
- [x] macOS
- [x] Linux
**Repro Steps**
1. Open up a normal Command Prompt (Terminal)
1. Create a Blazor Web App for WebAssembly
```
dotnet new blazor -int WebAssembly -o wasm
cd wasm/wasm
```
1. Publish the project with `dotnet publish`
1. Go to the publish folder and run `dotnet wasm.dll`.
1. Open the browser and go to the `http://localhost:5000/counter`
1. Open the browser developer console window
**Actual Result**
There is no any response and the console window contains some error
<img width="1300" height="750" alt="Image" src="https://github.com/user-attachments/assets/45f5ed1c-1e58-4bae-88a8-7b517a56ce4f" />
**Error Log**
```js
dotnet.runtime.fn94ls2wwa.js:3
[MONO] * Assertion at /__w/1/s/src/runtime/src/mono/mono/metadata/assembly.c:2718, condition `<disabled>' not met
Error
at Mc (dotnet.runtime.fn94ls2wwa.js:3:172298)
at dotnet.native.ggch313emy.wasm:0xac62
at dotnet.native.ggch313emy.wasm:0x43c51
at dotnet.native.ggch313emy.wasm:0x42301
at dotnet.native.ggch313emy.wasm:0x42422
at dotnet.native.ggch313emy.wasm:0x42465
at dotnet.native.ggch313emy.wasm:0x42438
at dotnet.native.ggch313emy.wasm:0x8cd9
at Module._mono_wasm_load_runtime [as mono_wasm_load_runtime] (dotnet.native.98v1chuo8c.js:8:113231)
at dotnet.runtime.fn94ls2wwa.js:3:188734
dotnet.runtime.fn94ls2wwa.js:3
MONO_WASM: mono_wasm_load_runtime () failed [object Object]
[NEW] Explain Console errors by using Copilot in Edge: click
to explain an error. Learn more
Don't show again
dotnet.runtime.fn94ls2wwa.js:3
Uncaught (in promise)
ExitStatus {name: 'ExitStatus', message: 'Program terminated with exit(1)', status: 1, silent: true}
dotnet.runtime.fn94ls2wwa.js:3
Uncaught (in promise)
ExitStatus {name: 'ExitStatus', message: 'Program terminated with exit(1)', status: 1, silent: true}
blazor.web.911ktl676v.js:1
Uncaught (in promise) Error: Failed to start platform. Reason: [object Object]
at Vr (blazor.web.911ktl676v.js:1:176030)
blazor.web.911ktl676v.js:1
Uncaught (in promise)
ExitStatus {name: 'ExitStatus', message: 'Program terminated with exit(1)', status: 1, silent: true}
```
**Expected Result:**
There is no any error when click counter button
**Note:**
1. This issue does not repro on Blazor Web Server app
2. This issue does not repro when `dotnet run`
3. This issue does not reproduce on the previous build
4. This issue also reproduces on 9.0 project after installing 10.0 RC 2
아쉽게도 .NET 10 RC2의 Blazor는 정적 페이지에서 Blazor의 캐싱 문제 해소를 위해 도입한 Fingerprint 관련 기능이 제대로 작동하지 않는 버그가 있습니다. RTM 준비 버전에서는 더 이상 발생하지 않지만, RC2에서는 오류가 발견되고 있으니 혹시 문제를 겪고 계시다면 Fingerprinting을 끄거나, RC1에서 GA 버전으로 기다렸다가 전환하시는 것이 좋겠습니다.
7 Likes