matthieu.dambrune@ -- Thanks for reporting this issue. Could you please provide the screencast of the issue and the device details where the issue is reproduced. That would help us in further triaging the issue.

Thanks in advance!

Screencast : https://drive.google.com/file/d/1SBxX0Xhyz0m-wXqgBm6PXlhTt0dcZo5C/view?usp=sharing

Screencast's details:

(before this a new version of the PWA has been deployed with logo & manifest.json update)

1 - launch the already installed PWA
2 - Wait for service worker custom update banner to appear 
3 - Click on "Mettre à jour" (i.e update)
4 - Close the PWA
5 - Open the PWA -> logo is still the same (old webmanifest)
6 - Remove the installed PWA
7 - Open chrome and reinstall the PWA -> PWA is installed with the current webmanifest (new logo visible)

As I said, logo and manifest are named `filename.[hash].[ext]` so it can't be a cache issue

Thank you for providing more feedback. Adding requester "pnangunoori@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Note: it's not specific to chrome for android. Add to desktop on chrome desktop does not update manifest as well.

#5: we haven't yet implemented updating on desktop yet, so it's not expected to work there right now.

pkotwicz/hanxi: can you follow up on this case on WebAPK updating? What schedule should the update be running on (i.e. should we expect an update at this point?)

We check for updates when a webapk is launched, but throttle to once every 3 days (IIRC)

Note: discussion about the spec https://github.com/w3c/manifest/issues/446

#7: thanks Yaron.

#8: can you check the old web app after a few days have passed and see if it's updated?

I will and I have no doubt it'll work as you said.

But when user is prompted to update the service worker, it's unexpected if visibles changes (icons, color) come after 3 days. And it's an issue if the start_url has to change immediatly because of others changes introduced by the new installed service worker

An command line flag "--check-for-web-manifest-update-on-startup" will avoid waiting and check whether an update is needed immediately after a WebAPK is launched. If the WebAPK needs an update, an update task will be scheduled to the background task scheduler. However, there is no way to monitor when the background task will be started. It would be scheduled at some point when Chrome is running but WebAPK isn't.