Closed
Bug 832361
Opened 12 years ago
Closed 12 years ago
When app update has invalid signature, we continue to report it as "1 update available" (and don't indicate that anything failed) after downloading & rejecting the update
Categories
(Firefox OS Graveyard :: Gaia, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 830913
People
(Reporter: dholbert, Unassigned)
Details
(Keywords: b2g-testdriver, unagi)
Currently, my unagi (build id 20130116230203) says "1 update available". When I tap the update, it pops up a dialog indicating that the update is for HERE Maps, w/ [Later][Download] buttons. I tap [Download]. There's a brief "0.00 bytes downloaded" in the notification dropdown screen, which increases to a few KB, and then all of a sudden it snaps back to "1 update available". In logcat, I see: { E/GeckoConsole( 524): Content JS INFO at app://system.gaiamobile.org/js/updatable.js:99 in anonymous: downloadError event, error code is INVALID_SIGNATURE } EXPECTED RESULTS: * Clearer indication (outside of logcat) of what happened / why the update isn't installing. Right now it just looks like we're broken and can't install updates. * (Possibly removing the "1 update available" notification after we find out that the available update is broken...?)
Reporter | ||
Updated•12 years ago
|
Component: General → Gaia
Summary: When app update has invalid signature, we continue to report it as "1 update available" after downloading & rejecting the update → When app update has invalid signature, we continue to report it as "1 update available" (and don't indicate that anything failed) after downloading & rejecting the update
Reporter | ||
Comment 1•12 years ago
|
||
I think one time (out of at least 5 times trying to download the update), I saw a notification appear at the bottom of my screen saying "There was an error installing the update" or something like that. If that message appeared more reliably, I'd consider this FIXED. Right now, I've only seen it one time, out of a bunch of download & install attempts (and it wasn't on the first attempt -- it was like on the third or fourth).
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
The underlying cause here may be the same as bug 830913, but the symptom here should be addressed separately.
Comment 4•12 years ago
|
||
(In reply to Chris Jones [:cjones] [:warhammer] from comment #3) > The underlying cause here may be the same as bug 830913, but the symptom > here should be addressed separately. Right. I'm going to leave bug 832408 open to track the bad UX issue.
Updated•12 years ago
|
tracking-b2g18:
? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•