Closed Bug 830051 Opened 11 years ago Closed 6 years ago

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

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g18+)

RESOLVED WONTFIX
Tracking Status
b2g18 + ---

People

(Reporter: jsmith, Unassigned)

References

Details

(Whiteboard: [UX-P?])

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.
UX sucks here, but I don't think we can block at this point. Definitely should track this though.
tracking-b2g18: --- → ?
Whiteboard: [UX-P?]
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.
No longer blocks: market-packaged-apps
Apparently this also happens when downloading fails when losing a network connection.
Summary: When downloading an 3rd party packaged app update fails due to a manifest mismatch error, we should notify the user of the failure, not silently fail → 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
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.
Depends on: 837193
Blocks: b2g-apps-v1-next
No longer blocks: b2g-app-updates
No longer blocks: b2g-apps-v1-next
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.