Skip to content

Cache manifest.webmanifest in PWA #54953

Closed
@tomasz-soltysik

Description

@tomasz-soltysik

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.

Activity

ghost added
area-blazorIncludes: Blazor, Razor Components
on Apr 4, 2024
added
bugThis issue describes a behavior which is not expected - a bug.
help wantedUp for grabs. We would accept a PR to help resolve this issue
and removed on Nov 13, 2024
shethaadit

shethaadit commented on Nov 30, 2024

@shethaadit
Contributor

Hi @mkArtakMSFT, I will work on this and raise PR soon. Could you please assign this issue to me? :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-blazorIncludes: Blazor, Razor ComponentsbugThis issue describes a behavior which is not expected - a bug.feature-pwaIssues related to building PWAs with Blazorhelp wantedUp for grabs. We would accept a PR to help resolve this issuetriaged

    Type

    Projects

    No projects

    Relationships

    None yet

      Participants

      @MackinnonBuck@shethaadit@tomasz-soltysik@mkArtakMSFT

      Issue actions

        Cache manifest.webmanifest in PWA · Issue #54953 · dotnet/aspnetcore