Closed
Bug 832684
Opened 11 years ago
Closed 11 years ago
Restarting a failed install doesn't get the new manifest if it changed
Categories
(Core Graveyard :: DOM: Apps, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: julienw, Unassigned)
References
Details
STR: * have a hosted+appcache webapp with a wrong path for the appcache manifest in the webapp manifest * install this app => it should fail * fix the bad path in the webapp manifest * restart the download from the app icon in the homescreen Expected: * it should now work Actual: * it still fails Workaround: * delete the app and install it again. Should not block but I think this should eventually be fixed.
Updated•11 years ago
|
Blocks: app-install
Comment 1•11 years ago
|
||
If you don't check for update, there's no way we can guess the appcache_path has changed in the manifest. Or I am missing something there?
Reporter | ||
Comment 2•11 years ago
|
||
This is more a proposition that an affirmation here, if you think this is a bad idea let's just close it wontfix. What I propose here is that if an app's installState is "pending", then when restarting a download, we should download the manifest again. I didn't tried with packaged apps, but the case is quite similar if the package_path is wrong. I don't know either for update cases.
Comment 3•11 years ago
|
||
I don't like that because there is no way to distinguish between a bad manifest and a server side issue. So it's very likely we will refetuch the manifest for no better result.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Updated•7 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•