 kjh2064
|
6b0bf5b78e
|
🔍 Analysis: Identified WASM loading failure and loading UI issue
TaxBaik CI/CD / build-and-deploy (push) Successful in 5m37s
Root cause discovered via Playwright automation testing:
1. **WASM Bootstrap Script**: ✅ Loads correctly
- Script path: _framework/blazor.webassembly.js
- Resolves to: /taxbaik/admin/_framework/blazor.webassembly.js
2. **WASM Assemblies**: ❌ Not loading (404)
- TaxBaik.Application.*.wasm: 404 (SRI check failed)
- TaxBaik.Domain.*.wasm: 404 (SRI check failed)
- TaxBaik.Web.Client.*.wasm: 404 (SRI check failed)
- .pdb files: 404 (SRI check failed)
3. **Result**: WASM runtime fails to initialize
- C# code never executes
- AdminShell component never renders
- hideLoading() never called
- Loading UI remains visible permanently
4. **Loading UI Issue** (User-identified)
- blazor-loading-overlay.show covers entire screen
- Should be hidden once WASM completes, but never does
- Creates perception of frozen/broken app
**Next Step**: Investigate static file serving configuration
- Check if _framework directory is accessible
- Verify SRI (Subresource Integrity) configuration
- Test direct WASM file access
**Testing Method**: Playwright automated browser testing
- Can execute JavaScript (unlike curl)
- Captures browser console errors
- Tracks resource loading failures
- Validates final rendering state
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
|
2026-07-04 20:57:25 +09:00 |
|