Closed
Bug 958939
Opened 11 years ago
Closed 11 years ago
[OTA][Helix] The items added in home screen are missing when device updates from v1.2 to v1.3
Categories
(Firefox OS Graveyard :: Gaia::Homescreen, defect)
Tracking
(blocking-b2g:1.3+, b2g-v1.3 verified)
Tracking | Status | |
---|---|---|
b2g-v1.3 | --- | verified |
People
(Reporter: hlu, Assigned: crdlc)
References
Details
(Keywords: dataloss, regression, Whiteboard: [systemsfe])
Attachments
(1 file)
The items added in home screen are missing when device updates from v1.2 to v1.3. (for example: website, marketplace installed items, E.me added items)
* Build Info (Both Gecko and Gaia)
Device Helix
Gaia 539a25e1887b902b8b25038c547048e691bd97f6
Gecko http://hg.mozilla.org/releases/mozilla-b2g26_v1_2/rev/e672faf1e6a1
BuildID 20140111004004
Version 26.0
ro.build.version.incremental=eng.wanglei.20131212.005845
ro.build.date=Thu Dec 12 00:58:58 CST 2013
* Reproduce Steps
1. Flash Helix device to v1.2 build from PVT
2. Change update URL to v1.3 (http://update.boot2gecko.org/helix/1.3.0/nightly/update_20140111004005.xml)
3. Add some websites to homescreen
4. Add some apps from marketplace to homescreen
5. Add some apps from E.me to homescreen
6. Perform check now to get the update notifcation
7. Download the update package
8. Install the upgrade package while the package is downloaded.
* Actual results:
The items added in home screen are missing when device updates from v1.2 to v1.3
* Expected results:
The items should be kept.
Updated•11 years ago
|
blocking-b2g: --- → 1.3?
Keywords: dataloss,
regression
Updated•11 years ago
|
Blocks: 1.3-data-migration
Updated•11 years ago
|
blocking-b2g: 1.3? → 1.3+
Updated•11 years ago
|
Whiteboard: [systemsfe]
Assignee | ||
Comment 2•11 years ago
|
||
I thought that Julien fixed this bug here bug 925461. I will try to reproduce it, thx
Flags: needinfo?(crdlc)
Updated•11 years ago
|
Assignee: nobody → crdlc
Target Milestone: --- → 1.3 C3/1.4 S3(31jan)
Comment 3•11 years ago
|
||
I checked, my change from bug 925461 is still there.
But bug 925461 was different: the items were still there _but_ you could not launch them. So it seems this is really a different bug.
Assignee | ||
Comment 4•11 years ago
|
||
We have just seen that it could be a DB VERSION issue
Assignee | ||
Updated•11 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 5•11 years ago
|
||
Attachment #8364323 -
Flags: review?(felash)
Comment 6•11 years ago
|
||
Comment on attachment 8364323 [details]
Patch v1
The code looks ok, I'm forwarding to Alexandre who'll check whether this fixes this bug and bug 953406.
Attachment #8364323 -
Flags: review?(felash) → review?(lissyx+mozillians)
Comment 7•11 years ago
|
||
I can confirm that it fixes at least bug 953406.
Comment 9•11 years ago
|
||
Is this also going to fix a device that already updated from 1.2 to 1.3?
Assignee | ||
Comment 10•11 years ago
|
||
(In reply to Axel Hecht [:Pike] from comment #9)
> Is this also going to fix a device that already updated from 1.2 to 1.3?
I think so but it should be tested. If this case is not fixed, we should fill a new bug thought
Comment 11•11 years ago
|
||
Comment on attachment 8364323 [details]
Patch v1
The code is simple enough and fixes this issue and bug 953406, this looks good to me !
Just have to hope that Travis will be green: https://travis-ci.org/mozilla-b2g/gaia/builds/17477320 :)
Attachment #8364323 -
Flags: review?(lissyx+mozillians) → review+
Comment 12•11 years ago
|
||
(In reply to Axel Hecht [:Pike] from comment #9)
> Is this also going to fix a device that already updated from 1.2 to 1.3?
I did an upgrade from 1.2 to 1.3 that replicates the issue and then I just pushed a fixed version of homescreen, restarted and it was okay. So I would answer yes.
Assignee | ||
Comment 13•11 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•11 years ago
|
status-b2g-v1.3:
--- → affected
Comment 14•11 years ago
|
||
(In reply to Axel Hecht [:Pike] from comment #9)
> Is this also going to fix a device that already updated from 1.2 to 1.3?
I think it does because the upgrade couldn't finish and therefore will be attempted again.
Comment 15•11 years ago
|
||
Sorry about this, I should have caught this in my review in bug 933752, no excuse. We learn every day!
Assignee | ||
Comment 16•11 years ago
|
||
Don't apologize Julien, everybody commit mistakes. Bugs are our friends. Without them we don't have job :) The most important is that it seems fixed. Go for another one! Thanks for your support to fix it mate!
Comment 17•11 years ago
|
||
Uplifted 93bea008761b534d8337f7819fc16ba526f686d2 to:
v1.3: 5e498acc8cae3251fd9683fc9b1b66d494bb9237
Comment 18•11 years ago
|
||
Just tested the latest update on my Keon on 1.3, and I can verify that it fixed the issue.
You need to log in
before you can comment on or make changes to this bug.
Description
•