Skip to content

Blazor WASM Standalone .webmanifest 404 error #51024

@silverlight-enjoyer

Description

@silverlight-enjoyer

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

Hello. I have a .net9 blazor wasm PWA app. I had some issues w/ caching and saw that there was a FIX in .net10 for re-including the webmanfiest. So I went ahead and added that. However, upon deployment I'm getting a 404 error when deploying to IIS.

Upon inspection, I can see that the default web.config is lacking a <remove fileExtension=".webmanifest" /><mimeMap fileExtension=".webmanifest" mimeType="application/json" />

Adding this manually fixes the console error. But, wouldn't this mean that new .net10 wasm pwa blazor apps will face this same issue? It doesn't seem like there's a easy fix for this for .net9 besides adding a custom web.config. However, I'm not sure what I would be missing from the "default" web.config template since it's autogenerated.

Expected Behavior

No response

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

No response

Anything else?

No response

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions