New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 818433 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug

Blocked on:
issue 819755



Sign in to add a comment

Incorrect splash layout used for webapk doesn't get updated

Reported by pedrocoe...@gmail.com, Mar 3 2018

Issue description

Android version: 7.0.0; Moto G (5) Plus
Chrome version: 64.0.3282.137

Site: https://mobile-staging.tvg.com

Steps to reproduce:
(1) Open the website
(2) Click install when prompted to add to home screen
(3) Open the app

Expected result:

It should display the splash screen using the large layout with the 512x512 icon

Actual result:

It shows the splash with the small layout using an older low res icon, presumably from and older version(4) of the webapk while in Chrome canary it installs the latest version(11) with the updated splash.

When I have tested with https://airhorner.com, which has specified in the manifest all the proper resolution icons, it always install the webapk with the splash for the small layout, even if there are 256x256 and 512x512 images. The only way to make it use the high-res image is by only specifying one with 512px in the manifest, and removing all the lower res images.

Is there any way to force the generation of a new webapk or to remove older versions from the Google Server? Thank you

 
Screenshot_20180302-193518.png
34.8 KB View Download
Cc: dominickn@chromium.org pkotw...@chromium.org mgiuca@chromium.org
+some relevant folks
Status: (was: Unconfirmed)
Thank you very much for your bug report.

It is possible to force the generation of a new WebAPK by renaming one of the icons.
e.g. splash_512.png -> splash2_512.png

Currently the server does not generate a new WebAPK when an icon is removed from the Web Manifest. It should. I have filed a server bug (tracked in a separate bug tracker) in order to fix this. The reason that you saw different behavior on Chrome Stable and Chrome Canary is that there is a different server for Chrome Stable and for Chrome Canary and they have separate WebAPK caches.

WebAPKs should use launcher icon on the splash screen. The trick of only using one large icon in the Web Manifest is not an intended feature.
I have filed  Issue 819755  to add support for larger icons on the splash screen. Hopefully we can get this into Chrome 67 (and yes we will eventually break the one large icon in the Web Manifest trick)
Blockedon: 819755
Owner: pkotw...@chromium.org
Status: Assigned
Updates on the server have been fixed
Status: Fixed (was: Assigned)

Sign in to add a comment