695739 - Unable to install a webapp on any non-Firefox browser

Status: VERIFIED FIXED

(addons.mozilla.org Graveyard :: Public Pages, defect, P3)

Description

[krupa raj[:krupa]]

steps to reproduce:
1. Load https://addons-dev.allizom.org/en-US/apps/app/test-webapp-11/ in Chrome.
2. Click on the install button.

expected behavior:
webapp can be installed on non-Firefox browsers

actual behavior:
Unable to install a webapp on any non-Firefox browser

Comment 1

[Andy McKay]

Does anyone know what JS libs or otherwise we need to install on a non-Firefox browser.

Comment 2

[Wil Clouser [:clouserw]]

CCing some people who might know

Comment 3

[Anant Narayanan [:anant]]

We noticed that the manifest fetcher at myapps.mozillalabs.com broke yesterday for some reason yet to be determined, causing this issue. Looking into this now.

Comment 4

[Anant Narayanan [:anant]]

Ian tracked down the problem to the VM hosting myapps.mozillalabs.com being unable to reach out to external networks. This is being tracked in an internal IT ticket.

Comment 5

[Jeff Balogh (:jbalogh)]

(In reply to Andy McKay [:andym] from comment #1)
> Does anyone know what JS libs or otherwise we need to install on a
> non-Firefox browser.

I think this involves including the webapp shim library, which I can't find a link to right now.

Comment 6

[Andy McKay]

What do you use on myapps.mozillalabs.com Anant? Then we can use the same on AMO.

Comment 7

[Anant Narayanan [:anant]]

The code running on myapps is this: https://github.com/mozilla/openwebapps/tree/develop/site

Among other things it provides:
- include.js, a HTML5-only implementation of the navigator.mozApps API for use in instances where the Firefox add-on is/can not be installed.
- A manifest fetcher (proxy) that allows include.js to fetch manifest files from remote servers to work around cross-origin limitations

Running the code on AMO infrastructure is certainly an option, but it is preferable to continue using the myapps domain as installed apps are stored in localStorage for that domain (which is where the dashboard is also hosted).

Comment 8

[Andy McKay]

Thanks I'll take a look. 

I doubt we want to have AMO traffic hitting myapps for code. 

And for the exact reasons you mentioned, we need to keep track of apps free and paid installed off of AMO, for that reason we'll need to be keeping it in localstorage on the AMO domain.

Comment 9

[Anant Narayanan [:anant]]

I don't think we want AMO to be aware of apps that the user installed from places other than AMO (other app stores, self-published apps etc). For this reason it is preferable to host include.js on the same domain we will provide a 'guest mode' dashboard of all apps the user has purchased everywhere. Currently, this is myapps.mozillalabs.com but will have to be moved to production soon; and preferably not on the same domain as AMO.

AMO is already keeping track of apps installed by the user that were installed from AMO itself and that is done independently of the mozApps API.

Comment 10

[Wil Clouser [:clouserw]]

Can someone tell me the next steps for this bug and the priority?

Comment 11

[Davor Spasovski [:spasovski]]

include.js was added so this should work

Comment 12

[krupa raj[:krupa]]

Able to install free apps on Safari and Chrome. Install for purchased apps doesn't work and is being tracked at bug 704534