Closed Bug 796471 Opened 12 years ago Closed 6 years ago

Installing a Web App, Updating the Manifest, Install App Again - App Does Not Update

Categories

(Firefox OS Graveyard :: Gaia::System, defect)

defect
Not set
normal

Tracking

(blocking-basecamp:-)

RESOLVED WONTFIX
blocking-basecamp -

People

(Reporter: ghtobz, Assigned: vingtetun)

Details

(Whiteboard: [label:mozapps])

[GitHub issue by jds2501 on 2012-08-10T05:53:58Z, https://github.com/mozilla-b2g/gaia/issues/3322]
## Build

* Device: Otoro
* Gaia: b6162954a4515114f24012b855f1e10cd8e9ad26
* Mozilla Central: 71acb417f8020fae803a7fb57a60d5b684943506

## Steps to Reproduce

1. Go to testmanifest.com
2. Install the web app
3. Change the name of the web app for the web app you've installed
4. Try installing that web app again

## Expected

The name of the app should change to the updated name in the app manifest.

## Actual

The name of the app does not change to the updated name in the app manifest.

## Additional Notes

Looks like a general problem that we aren't taking into account when we try to install an app already on the system that had it's app manifest change.
[GitHub comment by jds2501 on 2012-08-10T05:59:00Z]
cc @jcarpenter 

Leaving this to UX to make the call on this one if it blocks or not. Some notes worth noting:

1. Reinstalling of a web app won't be exposed by marketplace
2. App updates is tied to the system (a fundamental piece too) - in updating a "hosted" installed app on the system, we would probably hit this bug if the app manifest changes
3. Work around would require uninstalling the app and installing the app again to get the update
[GitHub comment by autonome on 2012-08-22T15:37:16Z]
Not blocking for V1. We can fix this as the app ecosystem grows larger.
Component: Gaia → Gaia::Apps Management
Component: Gaia::Apps Management → Gaia
Component: Gaia → Gaia::System
The problem seems to be still alive.
And reinstalling the app means to 1st remove the app (to fight the SAME_ORIGIN_CONFLICT), which is not the easiest thing to do on Aurora:
- rm the appropriate entry in ~/.local/share/applications (owa-http...)
- rm -r \{xxx...xxxx}
- fix the webapps.json
- rm -r ~/.http\;xxxx

The (local, client) manifest.webapp contains critical info (like the manifest.version) and it would be nice to know that the hosted app is up-to-date, client side in synch with the host repo. 

Not blocking, but it might be in the future.
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.