813743 - Set the correct URI for launching packaged webapps

Status: VERIFIED FIXED

(Firefox for Android Graveyard :: Web Apps (PWAs), defect, P1)

Description

[Wesley Johnston (:wesj)]

Packaged webapps launch using a special app://<uri> uri that is basically converted to a jar: uri, and just opens the file inside its zip [1]. We need to use that when creating shortcuts for apps on Android.

This is where things get a bit hairy. Right now, the first thing we do after the user approves installing an app is call into Java and ask it to create a profile for the new app:

http://mxr.mozilla.org/mozilla-central/source/mobile/android/chrome/content/browser.js#6813

We send that profile back to the webapps implementation in order for it to download any app cache information that it needs for first run. In this case, we DON'T want to create the shortcut yet, because we don't know the app's GUID yet, and hence don't know what launch url to use.

For webapps, I think we likely need to notify Gecko first, let it download the app into the webapps cache, and then try to get a GUID from that which we can pass to the shortcut.

cc'ing fabrice so he can give any more information about whether we can ignore app cache in this case, and what callbacks we need to make instead to get the apps GUID.

Comment 1

[Jason Smith [:jsmith]]

James - Does bug 813736 fix this bug?

Comment 2

[James Hugman [:jhugman] [@jhugman]]

Jason - yes. The fix for bug 813736 involves fixing this.

Comment 3

[Jason Smith [:jsmith]]

Okay, closing then.