If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[B2G][Homescreen] When updating a Flame to a custom build no preloaded bookmarks appear on the homescreen

RESOLVED INVALID

Status

Firefox OS
Gaia::Homescreen
RESOLVED INVALID
3 years ago
3 years ago

People

(Reporter: DerekH, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)
Bug Flags:
in-moztrap +

Firefox Tracking Flags

(b2g-v2.0 affected)

Details

(Whiteboard: [2.0-flame-test-run-1], URL)

Attachments

(1 attachment)

Created attachment 8437766 [details]
Preloaded Bookmarks

Description:
The facebook and youtube preloaded bookmarks do not appear on the homescreen when updating to a custom build and using T-Mobile or AT&T SIMs

Prerequisites: Include either a T-Mobile US SIM or AT&T US SIM in a Flame device. Setup a Flame build according to https://developer.mozilla.org/en-US/Firefox_OS/Developing_Firefox_OS/Market_customizations_guide


Repro Steps:
1) Update a Flame to BuildID: 20140609040203
2) Continue through the FTU
3) Observe the Homescreen

Actual:
No preloaded bookmarks appear on the homescreen, with either AT&T SIM or T-Mobile SIM

Expected:
The Facebook and Youtube preloaded bookmarks are present on the homescreen

Flame 2.0

Environmental Variables:
Device: Flame 2.0
Build ID: 20140609040203
Gaia: 954b77e12ef1d1cfdf8c9827af2842e5a525450c
Gecko: 9305a8ec77fe
Version: 32.0a1 (2.0) 
Firmware Version: v10G-2

User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 

Keywords: Customization, Update, Setup, Apps, Vertical Homescreen

Repro frequency: 100%
Link to failed test case: https://moztrap.mozilla.org/manage/case/9547/
See attached: Logcat, Screenshot (screenshots are taken directly after updating to custom build. No preloaded bookmarks are present)
This issue DOES occur on Buri 2.0

Environmental Variables:
Device: Buri Master
Build ID: 20140609223003
Gaia: a4a0cdf06568f0224956ea556cd2459e232a5d5a
Gecko: 9dc0ffca10f4
Version: 33.0a1 (Master) MOZ
Firmware Version: v1.2device.cfg


User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [VH-FC-blocking+]
Invalid. The test case here refers to bookmarks in the browser app, not the homescreen.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
QA Whiteboard: [VH-FC-blocking+]
Resolution: --- → INVALID
In previous test cases 9547 says to check the browser app for preloaded bookmarks, it has been changed to check the homepage for pre loaded bookmarks. Also on test case 9548: https://moztrap.mozilla.org/manage/case/9548/ it previously said to check the browser app, and has now been changed to say check the homescreen for bookmarks.

Checking on Buri 1.3 I found the proper preloaded facebook bookmark appear in the Browser app as well as the preloaded bookmark on the homescreen. On Flame 2.0 however, the facebook bookmark did not appear in either the browser app or the homescreen with the AT&T SIM or the T-Mobile SIM.



Buri 1.3 Environmental Variables

Environmental Variables:
Device: Buri 1.3
Build ID: 20140611052333
Gaia: 51dde56948192d920a2f888f5528ae73ee97c32d
Gecko: a55e22f592ac
Version: 28.0 (1.3) MOZ
Firmware Version: v1.2device.cfg

User Agent: Mozilla/5.0 (Mobile; rv:28.0) Gecko/28.0 Firefox/28.0

Comment 4

3 years ago
This case should be updated stating to check both Browser and Homepage bookmarks.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Flags: in-moztrap?(jthomas)
Test case has been updated in moztrap to say "Browser" instead of homepage:

https://moztrap.mozilla.org/manage/case/9547/
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Flags: in-moztrap?(jthomas)
Flags: in-moztrap+
You need to log in before you can comment on or make changes to this bug.