-
Notifications
You must be signed in to change notification settings - Fork 10.6k
Labels
area-blazorIncludes: Blazor, Razor ComponentsIncludes: Blazor, Razor ComponentsbugThis issue describes a behavior which is not expected - a bug.This issue describes a behavior which is not expected - a bug.feature-pwaIssues related to building PWAs with BlazorIssues related to building PWAs with Blazorhelp wantedUp for grabs. We would accept a PR to help resolve this issueUp for grabs. We would accept a PR to help resolve this issuetriaged
Milestone
Description
Is there an existing issue for this?
- I have searched the existing issues
Describe the bug
After file extension change done in #43756, Web Manifest is no longer added to offline cache.
Prior to this change it had json extension which is included.
Expected Behavior
Web Manifest should be added to offline cache by default service worker implementation.
Steps To Reproduce
- Create new project from Blazor template, with PWA option selected.
- Run published app and let service worker install.
- Check if manifest.webmanifest is in offline cache
Exceptions (if any)
No response
.NET Version
No response
Anything else?
Adding /\.webmanifest$/ to offlineAssetsInclude in service-worker.published.js should fix this.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area-blazorIncludes: Blazor, Razor ComponentsIncludes: Blazor, Razor ComponentsbugThis issue describes a behavior which is not expected - a bug.This issue describes a behavior which is not expected - a bug.feature-pwaIssues related to building PWAs with BlazorIssues related to building PWAs with Blazorhelp wantedUp for grabs. We would accept a PR to help resolve this issueUp for grabs. We would accept a PR to help resolve this issuetriaged