830051 - When downloading an 3rd party packaged app update fails due to an error (e.g. network failure, packaged app error) we should notify the user of the failure, not silently fail

Status: RESOLVED WONTFIX

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

Description

[Jason Smith [:jsmith]]

Build: B2G 18 1/12/2013
Device: Unagi

Steps:

1. Install a small packaged app with manifest webapp matching respective fields in the mini-manifest
2. Update the packaged app on the server that contains a manifest webapp that has fields not matching respective fields in the mini-manifest
3. Check for updates (manual or automatic)
4. Confirm the update

Expected:

The update should fail as soon as we find the manifest mismatch. If it fails, we should report a useful error message to the user.

Actual:

The update fails, but it's a silent failure with an immediate reprompt for the update. This is a poor UX, as the user is left confused why they need to try to download the update again without knowing that the update "officially" failed.

Comment 1

[Jason Smith [:jsmith]]

UX sucks here, but I don't think we can block at this point. Definitely should track this though.

Comment 2

[Jason Smith [:jsmith]]

The simple fix to this problem would probably be watching the download error that's fired back and knowing to report a download failure message to the user similar to what we do for app install.

Comment 3

[Jason Smith [:jsmith]]

Apparently this also happens when downloading fails when losing a network connection.

Comment 4

[Julien Wajsberg [:julienw]]

Probably Bug 837193 would help a lot here.

Also, the error is never silent as we should display a small banner. Yet it's right that the user can miss it.

Comment 5

[BMO Automation]

Firefox OS is not being worked on