Missing Manifest after azure deploy

[X0RN0T]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

Vanilla Blazor WebAssembly-App gets started locally on the iis the manifest gets deployed correct. If the Blazor WebAssembly-App gets deployed on azure the manifest gets missing. Browser shows

Manifest fetch from https://-------------------------------.azurewebsites.net/manifest.webmanifest failed, code 404

Because its missing the application can`t start as PWA.

Expected Behavior

Manifest should be there and in correct place

Steps To Reproduce

Create Blazor WebAssembly-App with PWA, deploy to azure

Exceptions (if any)

workaround or fix

.NET Version

10

Anything else?

[X0RN0T]

I fixed it by adding a web.config in the wwwroot folder with the content

<?xml version="1.0" encoding="utf-8"?> <configuration> <system.webServer> <staticContent> <mimeMap fileExtension=".webmanifest" mimeType="application/manifest+json" /> </staticContent> </system.webServer> </configuration>

Maybe this should be moved to the template of the Blazor WebAssambly App when PWA is checked

[dotnet-policy-service]

Tagging subscribers to 'arch-wasm': @lewing, @pavelsavara
See info in area-owners.md if you want to be subscribed.