3gakugd@ -- Thanks for reporting this issue. Could you please share any sample page to reproduce the same at TE's end along with the screen cast of the issue, which will help us in understanding the issue better.

Also, share the device details where the issue is observed.

Thanks in advance!

Hi,

It sounds like a bug regarding updating the manifest on the WebAPK server. As far as I know, if the manifest changes, the browser should request a new WebAPK containing the new details, when the user re-installs the application. However, I'm skeptical due to this line:

> 1. Prepare the page, that has service worker to catch fetch event, manifest.json, index page.

If your service worker is caching your manifest, it's possible that there is a fault in the SW where it isn't seeing the updated manifest. If the browser isn't seeing the new manifest, then it won't send the new details to the server. Can you check the Application tab in the Dev tools to see if it is actually seeing the new manifest file?

Thank you for responses.

> Could you please share any sample page to reproduce the same at TE's end along with the screen cast of the issue, which will help us in understanding the issue better.
I will create sample page and record screen by today (JST). However, I could not understand 'TE' means. What does it mean?

> share the device details where the issue is observed.
My device is HTC U11 Unlocked (Japan), it runs Android that has version 8.0, build version '2.53.454.4 9.0_g CL1028801 release-keys' and security patch level '2018/1/1'.

> Can you check the Application tab in the Dev tools to see if it is actually seeing the new manifest file?
Yes. My service worker was crated to be recognized as PWA, so it always returns void to cause the default behaviour. If the name field on manifest.json changed, browser shows new name on dialog displayed when 'add to home screen button' pressed.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

> I will create sample page and record screen by today (JST). However, I could not understand 'TE' means. What does it mean?

I think it means Test Engineering (basically, "at our end").

I can't reproduce this bug.
- The share target spec has changed. "url_template" is no longer part of the share target web manifest spec. https://wicg.github.io/web-share-target/
  The new share target Web Manifest format:
  "share_target": {
    "action": "share.html",
    "params": {
      "title": "name",
      "text": "description",
      "url": "link"
    }
  }

- I tried doing installs with the same manifest URL and changing the contents of the manifest. The installed WebAPK respected the updated manifest.

3gakugd@:
- Can you try again to check whether the buggy behaviour is still present on an up to date version of Chrome? (Chrome 71 or newer)
  - If you can still reproduce the buggy behaviour can you provide more details?
    - Is manifest.json respected the first time that you add the page to the home screen?
    - In the cases that manifest.json is not respected, what occurs? Does the newly installed APK not handle share intents anymore?
- Have you tried navigating to the manifest URL prior to adding the page to the home screen to ensure that the old Web Manifest is not cached in Chrome's HTTP cache?