I have a few of instances of Discourse running for different projects. They are pretty much identical, other than a couple of minor CSS differences, but are behaving differently when I try to use the “Add to homescreen” option on chrome for android. The majority work without a hitch (imitating a native app; splash screen, no URL bar, etc), however two instances seem to simply put a shortcut on the homescreen and open up in a new tab in chrome. Are there any specific criteria that I might have neglected to set up in the two misbehaving that might be causing this? (I’ve tested it across a couple of devices, so I’m confident I’m not the only one experiencing it). [image] [image]

[image] auryn_macmillan: I’m the admin for both. Hahaha, you should’ve mentioned it earlier :stuck_out_tongue:. The only SiteSettings that we use are title and apple_touch_icon_url. app/controllers/metadata_controller.rb aa4dccd0a def manifest render json: default_manifest.to_json end def opensearch render file: "#{Rails.root}/app/views/metadata/opensearch.xml" end private def default_manifest { name: SiteSetting.title, short_name: SiteSetting.title, display: 'standalone', orientation: 'portrait', start_url: "#{Discourse.base_uri}/", background_color: "##{ColorScheme.hex_for_name('secondary')}", theme_color: "##{ColorScheme.hex_for_name('header_background')}", icons: [ { Do you use any plugins? The push notifications one mess with this controller I think.

As said here you need https. Can you share the links?

Both are using https I believe: https://forum.gnosis.pm/ https://forum.ether.camp/

[image] Falco: Maybe they forgot to set a required field. What are the required fields? And how would I go about fixing this?

My best guess is they didn’t set the apple_touch_icon_url SiteSetting. Try sending a PM to an admin and asking then.

I’m the admin for both. apple_touch_icon_url for https://forum.gnosis.pm is: [image] mobile_logo_url for https://forum.gnosis.pm is: [image] [image]

[image] Falco: Do you use any plugins? The push notifications one mess with this controller I think. Yeah I have the push notifications plugin installed on both, I’ll try rebuilding one without and see if that fixes it.

[image] auryn_macmillan: Yeah I have the push notifications plugin installed on both, Hoho, found it! I think that just configuring the plugin may work. You either install and fill all the fields or uninstall.

There is a field called gcm_sender_id somewhere. However, this should not happen anyway. This may fix it (still need some testing): https://github.com/discourse/discourse-push-notifications/pull/7

Criteria to ensure Discourse instance will work as a Chrome webapp on mobile

Product Support

Falco (Falco) September 13, 2016, 10:07pm 4

Both manifest.json is somehow broken. How they did it is beyond me.

Maybe they forgot to set a required field…

Topic		Replies	Views
Add to homescreen banner on Android Announcements feedback	68	20609	November 6, 2017
Fully support Android Chrome's "Add to Homescreen" Feature	28	14623	April 20, 2016
Android app can't see my discourse Product Support	21	2693	April 19, 2019
Meta's iOS "Add to Home Screen" icon is not good Site feedback	16	2863	April 4, 2023
Push Notifications Not functioning Product Support	22	3829	May 3, 2019

Criteria to ensure Discourse instance will work as a Chrome webapp on mobile

Related topics