Closed Bug 1039646 Opened 11 years ago Closed 11 years ago

[B2G][Homescreen][OTA]Pages are not preserved after OTA from 1.3 to 2.0

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v2.0 affected, b2g-v2.1 unaffected)

RESOLVED DUPLICATE of bug 1039968
Tracking Status
b2g-v2.0 --- affected
b2g-v2.1 --- unaffected

People

(Reporter: astole, Unassigned)

References

Details

(Keywords: smoketest, Whiteboard: [systemsfe])

Attachments

(3 files)

Attached file logcat
The Homescreen layout when creating new pages is not preserved after updating the device from 1.3 to 2.0 Repro Steps: 1) Update a Flame to v122 and latest 1.3 Gaia 2) Move a couple apps to a 3rd page 3) Turn on Wifi 4) Open Settings > Device Information 5) Select 'Check for updates' 6) When update found select the notifications menu 7) Download and install the update 8) Unlock phone and proceed to Homescreen Actual: 3rd page layout is not preserved on the Homescreen Expected: All page layouts are preserved after OTA 2.0 Environmental Variables: Device: Flame 2.0 BuildID: 20140716000201 Gaia: 5f8b1b8a2da9e3b531eee817a669f57fa4d9b9c6 Gecko: 913827496f65 Version: 32.0a2 Firmware Version: v122 Repro frequency: 100% See attached: logcat
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Smoketest blocker, nominating to block 2.0.
blocking-b2g: --- → 2.0?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
The apps in question were Clock, Calendar, and Email. They were grouped with the rest of the system apps in 2.0 instead of in their own page as it was setup in 1.3.
Assignee: nobody → crdlc
Status: NEW → ASSIGNED
Please test it again after uplifting bug 1037556 to 2.0. It works fine for me, please see attached videos
Assignee: crdlc → nobody
Status: ASSIGNED → NEW
Whiteboard: [systemsfe]
This may be a dupe, then. Let's wait until bug 1037556 is uplifted.
Blocks: 1015336
blocking-b2g: 2.0? → ---
QA Whiteboard: [QAnalyst-Triage+] → [VH-FL-blocking-][VH-FC-blocking?][QAnalyst-Triage+]
See Also: → 1037556
See Also: → 1039968
Johan, you can take a look at this bug 1039968 very related to this one
I gonna close this one as dupe of bug 1039968 because the root cause seems the same in both cases
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: