XF 2.2 Can't install PWA on Chrome (desktop)

Mr Lucky

Well-known member
What am I missing?

  • I have the short title
  • I have the two icons, 192 and 512
  • I have SSL/https.

With xenforo I see a + icon on Chrome to install an app, but not on my dev forum.

Could it be because it is IP protected?
 
It is there now

Code:
{
    "name": "CafeSaxophone Forum",
    "short_name": "CafeSaxophone",
    "description": "Saxophones, music, general chat",
    "icons": [
        {
            "src": "https:\/\/cafesaxophone.com\/styles\/petecafe\/cafe-app192.png",
            "sizes": "192x192"
        },
        {
            "src": "https:\/\/cafesaxophone.com\/styles\/petecafe\/cafe-app512.png",
            "sizes": "512x512"
        }
    ],
    "lang": "en-US",
    "dir": "LTR",
    "display": "minimal-ui",
    "scope": "\/",
    "start_url": "\/?_pwa=1",
    "background_color": "#ececec"
}
 
Still nothing
what do you mean 'nothing'? how this now looks like?

screenshot-2020-07-27-at-18-47-23-png.231445
 
It now looks like this:


Screenshot 2020-07-27 at 22.16.23.png


webmanifest.php

is this

Code:
{
    "name": "CafeSaxophone Forum",
    "short_name": "CafeSax",
    "description": "Saxophones, music, general chat",
    "icons": [
        {
            "src": "https:\/\/cafesaxophone.com\/styles\/petecafe\/cafe-app192.png",
            "sizes": "192x192"
        },
        {
            "src": "https:\/\/cafesaxophone.com\/styles\/petecafe\/cafe-app512.png",
            "sizes": "512x512"
        }
    ],
    "lang": "en-US",
    "dir": "LTR",
    "display": "minimal-ui",
    "scope": "\/",
    "start_url": "\/?_pwa=1",
    "background_color": "#ececec"
}

(NB: Not sure if it matters, but path to icons is/was in live site, but makes no difference now I have moved to dev site anyway)
 
Last edited:
It's worth mentioning that your live site has this in it:
Code:
 <link rel="manifest" href="/site.webmanifest">
This is something that has presumably been added by your style, but it's conflicting with 2.2 adding its own manifest.
 
It's worth mentioning that your live site has this in it:
Code:
 <link rel="manifest" href="/site.webmanifest">
This is something that has presumably been added by your style, but it's conflicting with 2.2 adding its own manifest.
Yes I'm about to look into why it is seeing that, but just restopred and re-upgraded the test site.
 
The issue I encountered was not using a PNG, SVG or WebP image. I was using a JPG, developers tools manifest section will state the image type is insufficient or something to that effect.
 
It's worth mentioning that your live site has this in it:
Code:
 <link rel="manifest" href="/site.webmanifest">
This is something that has presumably been added by your style, but it's conflicting with 2.2 adding its own manifest.
Found it. It was in a custom template edit (needed?) for Android favicons

Code:
<link rel="manifest" href="/site.webmanifest">

contents:

Code:
{
    "name": "",
    "short_name": "",
    "icons": [
        {
            "src": "/android-chrome-192x192.png",
            "sizes": "192x192",
            "type": "image/png"
        },
        {
            "src": "/android-chrome-256x256.png",
            "sizes": "256x256",
            "type": "image/png"
        }
    ],
    "theme_color": "#ffffff",
    "background_color": "#ffffff",
    "display": "standalone"
}

I'm not sure that's very important so I'll just ditch it, or is there a way to get the links to those icons added to the default webmanifest?
 
Last edited:
We already add the needed icons in the default webmanifest, and you can make sure you have populated them in the Style properties > Basic options style property group. It looks like you have already done this.

It's worth noting that many specs have evolved in many different ways over the years as many devices with different OS versions and capabilities have changed.

The ones we ask for under Basic options should be sufficient for all use cases as far as I am aware.
 
It looks like you have already done this.

Almost ;)

The manifest is missing maskable icons and Lighthouse complains about this (as does Google play when submitting an APK for such a manifest)
All interesting info. I generated favicons form here:


And from that I have uploaded:

Screenshot 2020-08-03 at 18.08.57.webp

with this in head (which was causing the issue here.

Code:
<link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="/favicon-16x16.png">
<link rel="manifest" href="/site.webmanifest">
<link rel="mask-icon" href="/safari-pinned-tab.svg" color="#5bbad5">
<meta name="msapplication-TileColor" content="#da532c">
<meta name="theme-color" content="#ffffff">

It will be good to ditch all (or nearly all) that.
 
Top Bottom