adobe / adobe/aem-core-wcm-components

Enabling PWA adds manifest.webmanifest in head but file doesnt actually exists

Open
#1,968 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
Java
Stars
795
Forks
775
Avg merge
3d 22h
Merged PRs (30d)
8

Description

**Current Behavior**
When enabling PWA feature in page property and authoring fields we can observe in the view as publish page that the service worker is present but not the manifest.webmanifest file. In the console we can see error for file not being found. We attempted with Weekend project as well and same issue. Are we suppose to create this file or enabling PWA suppose to generate this file?

**Expected behavior/code**
Expectation is by enabling the manifest.webmanifest file will be created and stored somewhere we can view. On page load the page should be able to retrieve this file.

**Environment**
- AEMaaCS SDK latest
- Core Components version latest
- Java(TM) SE Runtime Environment 18.9 (build 11.0.12+8-LTS-237)

**Possible Solution**
n/a

**Additional context / Screenshots**
![image](https://user-images.githubusercontent.com/99004282/152481689-37e39125-3194-4232-994b-c26525391884.png)

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue by enabling the PWA feature in the page properties and authoring fields, then inspect the published page for the service worker and manifest.webmanifest request. Determine whether the manifest should be generated or manually created; done means the expected manifest.webmanifest exists and can be retrieved without a not-found error.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
frontend, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.