Closed
Bug 859307
Opened 12 years ago
Closed 12 years ago
[updates] wrong behavior when the manifest changes but not the packaged zip
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Tracking
(blocking-b2g:tef+, firefox21 wontfix, firefox22 wontfix, firefox23 fixed, b2g18 fixed, b2g18-v1.0.0 wontfix, b2g18-v1.0.1 fixed)
People
(Reporter: julienw, Assigned: fabrice)
References
Details
Attachments
(1 file)
1.45 KB,
patch
|
ferjm
:
review+
julienw
:
feedback+
|
Details | Diff | Splinter Review |
STR:
* install a packaged app where you control the files
* change the manifest.webapp (for example: increment the version string)
* check for update, accept the update
Expected:
* the update happens
Actual:
* the update fails, and the notification stays at 0 bytes forever
According to [1], we get a downloadapplied event but no downloadsuccess (because |aSuccess| is not called).
I don't know if we should fix gecko (sending a downloadsuccess event before downloadapplied) or gaia (getting downloadapplied should remove the notification as a downloadsuccess would do).
I'd rather fix gecko because this feels inconsistent to me, but Fabrice, Étienne, what do you think ?
Asking tef? too. This does not brick the phone but this makes a broken notification stay forever until the phone is rebooted.
[1] http://mxr.mozilla.org/mozilla-central/source/dom/apps/src/Webapps.jsm#2226
Reporter | ||
Updated•12 years ago
|
Flags: needinfo?(etienne)
Reporter | ||
Updated•12 years ago
|
Flags: needinfo?(fabrice)
Comment 1•12 years ago
|
||
Hitting this as an end user is very uncomfortable: you think (I did) update failed :/
Updated•12 years ago
|
Blocks: b2g-app-updates
Assignee | ||
Comment 2•12 years ago
|
||
I don't mind sending a downloadsuccess before downloadapplied from gecko. I also agree this should be tef+.
Flags: needinfo?(fabrice)
Assignee | ||
Comment 3•12 years ago
|
||
Julien, that works for me, but please verify.
Assignee: nobody → fabrice
Attachment #734842 -
Flags: review?(ferjmoreno)
Updated•12 years ago
|
blocking-b2g: tef? → tef+
Reporter | ||
Updated•12 years ago
|
Flags: needinfo?(etienne)
Reporter | ||
Comment 4•12 years ago
|
||
This fixes it for me too !
Reporter | ||
Updated•12 years ago
|
Attachment #734842 -
Flags: feedback+
Updated•12 years ago
|
Attachment #734842 -
Flags: review?(ferjmoreno) → review+
Assignee | ||
Comment 5•12 years ago
|
||
Comment 6•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → B2G C4 (2jan on)
Comment 7•12 years ago
|
||
https://hg.mozilla.org/releases/mozilla-b2g18/rev/8faf9b364a8f
https://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/935ff9a97f7b
status-b2g18:
--- → fixed
status-b2g18-v1.0.0:
--- → wontfix
status-b2g18-v1.0.1:
--- → fixed
status-firefox21:
--- → wontfix
status-firefox22:
--- → wontfix
status-firefox23:
--- → fixed
Comment 8•12 years ago
|
||
This patch definitely isn't working for me on the b2g 18 branch.
I tried a test case that did the following:
1. Install a packaged app with icon X referenced in the package zip with state1.zip as name
2. Change the packaged app to have the same name, but icon Y is now referenced
3. Check for updates
Result - I'm not finding an update at all.
Keywords: verifyme
You need to log in
before you can comment on or make changes to this bug.
Description
•