796459 - References to packaged apps use app://{hex address} as the location

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia, defect)

Description

[GH to BZ]

[GitHub issue by jds2501 on 2012-08-07T05:39:08Z, https://github.com/mozilla-b2g/gaia/issues/3205]
## Build

* Device: Otoro
* Gaia: ed06bdb7caaa35873970c9955ace28beab655202
* Mozilla Central: 0379f69ee8dd1c9f58c78d7f500231cba099139d

## Steps

1. Go to http://people.mozilla.org/~fdesre/openwebapps/test.html
2. Select Install Packaged App

## Expected

The prompt should you to confirm if you would like to install the app from X origin, which should be readable and interpretable by an end-user.

## Actual

The prompt does indeed come up, but from X origin piece comes up as app://{hex address}. The hex address likely won't be interpretable by an end-user. Is there something better we could do here for packaged apps?

cc @fabricedesre Any ideas?

Comment 1

[GH to BZ]

[GitHub comment by jds2501 on 2012-08-07T05:48:28Z]
Screenshot - http://imageshack.us/photo/my-images/191/20120807054547.png/

Comment 2

[GH to BZ]

[GitHub comment by jds2501 on 2012-08-08T05:20:08Z]
It looks we generally refer to the app always by app://{hex address} in general, as I saw this happen when I tried installing an app that launched to content that did not exist. We should do something better here, as a hex address (if a user hits this) is bound to confuse a user.

Comment 3

[GH to BZ]

[GitHub comment by fabricedesre on 2012-08-08T05:44:53Z]
This is caused by the fact that packaged apps have no origin, so we create one with a UUID.

Comment 4

[GH to BZ]

[GitHub comment by jds2501 on 2012-08-08T06:02:57Z]
@fabricedesre Ah okay, makes sense. If the origin itself is not in an end-user readable format, then what string should we show instead? Take these two use cases for example:

1. Installing a package app - the prompt that comes up
2. Launching content that does not exist

For (1), a possible idea is to throw out the from <origin> piece, although I have a feeling that was put there originally for permissions needs, so not sure on that idea. Maybe Lucas has an idea here? I'll fire him a message and cc you and Anant on the email.

Comment 5

[GH to BZ]

[GitHub comment by jds2501 on 2012-08-09T20:46:03Z]
To bring details from the email thread - in general we should not expose the app://{UUID} at any point when using a packaged app to an end user. As for what is the mitigation in the UI, that's still being figured out.

Comment 6

[GH to BZ]

[GitHub comment by jds2501 on 2012-08-09T21:34:36Z]
@jcarpenter UX input needed. For a packaged app, is showing "Do you want to install app name from host" okay?

Comment 7

[GH to BZ]

[GitHub comment by jcarpenter on 2012-08-15T15:45:34Z]
@jds2501 Yes, that works.

Comment 8

[GH to BZ]

[GitHub comment by autonome on 2012-08-20T15:17:41Z]
Blocking, since this will happen to any app not coming from our marketplace.

Comment 9

[GH to BZ]

[GitHub comment by jcarpenter on 2012-09-30T23:26:56Z]
Related: [[System] Implement new app install flows](https://github.com/mozilla-b2g/gaia/issues/4948)

Comment 10

[[:fabrice] Fabrice Desré]

Closing since this issue disappears with the use of mini-manifests to install packaged apps.