Closed Bug 833564 Opened 13 years ago Closed 7 years ago

When checking if an update is available, we should check that the package_path or appcache_path to update to is valid if the etag has changed

Categories

(Core Graveyard :: DOM: Apps, defect)

Product:
Core Graveyard
Component:
DOM: Apps
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: jsmith, Unassigned)

Details

Currently, if the mini-manifest or webapp manifest changes from a valid package_path or appcache_path to a path that does not exist (i.e. 404), we still fire an update available, even though the update will always be invalid. Applying the update will fail, but we could have stopped this process earlier if we checked for validity of the package_path and appcache_path during the check for updates process. So I'd suggest checking that the path exists before indicating an update is available.
Blocks: b2g-app-updates
Blocks: b2g-apps-v1-next
No longer blocks: b2g-app-updates
No longer blocks: b2g-apps-v1-next
Product: Core → Core Graveyard
Core Graveyard / DOM: Apps is inactive. Closing all bugs in this component.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.