Closed Bug 1063063 Opened 11 years ago Closed 11 years ago

[OTA] After updating to the latest build, FMD is missing from Settings

Categories

(Firefox OS Graveyard :: FindMyDevice, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: marcia, Unassigned)

Details

Attachments

(2 files)

Flame, while running: Gaia a47ecb6368c015dd72148acde26413fd90ba3136 SourceStamp 757931d0149e BuildID 20140904000203 Version 34.0a2 base: v123 STR: 1. Flash the 9-3 build 2. Perform an OTA to the 9-4 3. Observe the attached screenshot FMD is missing from the Account Settings. Rebooting the device restores the menu item.
I was unable to reproduce this bug when starting with the 20140903000204 build then updating to the 20140908000204 build. Actual Results: Find My Device is available in Settings after OTA update. Repro attempts: 0/5 Device: Flame 2.1 (Nightly) Build ID: 20140903000204 Gaia: fbb297c39aab5f17b179533d2a9a6c5166b2c197 Gecko: fb5e796da813 Version: 34.0a2 (Master) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Device: Flame 2.1 (Nightly) Build ID: 20140908000204 Gaia: a8e4d26555e5713ec6c72270cfd0cfabc096a0d3 Gecko: 746f24f9d21d Version: 34.0a2 (Master) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Leaving qawanted tag for other testers to attempt.
removing [OTA] from subject. I did a fresh flash on this build and see that FMD option is missing, just like the attachment. no logcat that has any relevant data Gaia 5fa8624aaa29b12b82afa6e3805aba39c29482bd Gecko https://hg.mozilla.org/releases/mozilla-aurora/rev/9cd6d7944c3e BuildID 20140905123006 Version 34.0a2 ro.build.date Fri Sep 5 15:42:28 EDT 2014 ro.bootloader L1TC00011660 ro.build.version.incremental eng.cltbld.20140905.154218
Summary: [OTA] After updating to the latest build, FMD is missing from Settings → After updating to the latest build, FMD is missing from Settings
[Blocking Requested - why for this release]:
blocking-b2g: --- → 2.1?
I've tried flashing today's aurora user build and aurora engineer build onto my flame, and can't reproduce in either case. I am using the flash tool[1], not sure if that matters here. If other QA testers are able to repro, could you please give details of how you flashed the device? This is the third FMD bug currently open which indicates fundamental brokenness on the aurora builds, and I'm not yet sure what the root cause might be. (The other bugs are bug 1058729 and bug 1058978) Build info: Gaia c7b55ed3be126b1f5f3d9cdd0277c365a6652d29 Gecko https://hg.mozilla.org/releases/mozilla-aurora/rev/956b152e6d21 BuildID 20140909000204 Version 34.0a2 ro.build.date Tue May 20 09:29:20 CST 2014 ro.bootloader L1TC200110G0 ro.build.version.incremental 94 [1] https://github.com/Mozilla-TWQA/B2G-flash-tool/blob/master/flash_pvt.py
I'm also not able to reproduce this after flashing today's m-c builds, either user or engineer, onto my flame. Tony, what specific steps did you take when you reproduced this on your device? Gaia 4acd3e69b263b54f4111e3586ff4ade84b49b4da Gecko https://hg.mozilla.org/mozilla-central/rev/6b8da5940f74 BuildID 20140909040219 Version 35.0a1 ro.build.date Tue May 20 09:29:20 CST 2014 ro.bootloader L1TC200110G0 ro.build.version.incremental 94
Flags: needinfo?(tchung)
In a separate discussion in another meeting today, jsmith was mentioning that there was weirdness being seen in the Settings API over the last week. Wondering if that is affecting some of these bugs.
Qanalysts, can you try reproducing with a fresh flash? I'm going to try again. it might be a series of different steps of the user before hitting this hidden/missing FMD setting. I'll try to reproduce as well on today's KK build.
Flags: needinfo?(tchung) → needinfo?(jmitchell)
Marcia and I tried it on today's 9/10 build, and can't see reproduce. going to resolve WFM and clear blocking flag. will reopen and renom if we can get a steady repro. Gaia 77a475a68d3a17ca74cae64bc63e3263b353156a Gecko https://hg.mozilla.org/integration/b2g-inbound/rev/9e8b94eb578c BuildID 20140910053006 Version 35.0a1 ro.build.date Wed Sep 10 08:45:53 EDT 2014 ro.bootloader L1TC00011660 ro.build.version.incremental eng.cltbld.20140910.084543
blocking-b2g: 2.1? → ---
Flags: needinfo?(jmitchell)
Keywords: qawanted
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Attached image 2014-09-10-15-38-59.png
Unfortunately, I see this again today on Master. Attaching a screenshot. This phone was on yesterday's nightly, and I performed an OTA to today's nightly and as you can again FMD is missing. Restarting the device restores the behavior.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Marcia - Is this OTA problem reproducible on 2.1, or just master? Also, adjusting the bug summary to include [OTA].
Summary: After updating to the latest build, FMD is missing from Settings → [OTA] After updating to the latest build, FMD is missing from Settings
Doh. See question in my previous comment
Flags: needinfo?(mozillamarcia.knous)
(In reply to Jared Hirsch [:_6a68] [NEEDINFO pls] from comment #11) > Marcia - Is this OTA problem reproducible on 2.1, or just master? > > Also, adjusting the bug summary to include [OTA]. Jared: I haven't seen this on Master recently, nor have I seen it on 2.1. When it was happening it did happen occasionally with a fresh flash as well as OTA - see Tony's comment 3.
Flags: needinfo?(mozillamarcia.knous)
oh, cool. Marking as closed, then. Feel free to reopen if it can be reproduced :)
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: