Closed Bug 1022992 Opened 10 years ago Closed 10 years ago

FMD Doesn't Always Show as 'Enabled' in Settings Even When It Is

Categories

(Firefox OS Graveyard :: FindMyDevice, defect)

x86
macOS
defect
Not set
normal

Tracking

(blocking-b2g:2.0+, b2g-v2.0 verified, b2g-v2.1 verified)

VERIFIED FIXED
2.0 S4 (20june)
blocking-b2g 2.0+
Tracking Status
b2g-v2.0 --- verified
b2g-v2.1 --- verified

People

(Reporter: kglazko, Assigned: ggp)

References

Details

Attachments

(4 files)

This typically happens after a phone restart. After restarting phone, head to Settings. You will see Find My Device under Account Management, and there will be no disabled nor enabled text under 'Find My Device'.

When you click on FMD, if it is enabled as it was in my case, you will see that it is enabled with the blue toggle bar. However, it will flash the sign in screen for about a minute before showing the toggle bar.

When you go back to the settings, Enabled will display as it is supposed to. If you lock the phone and head to Settings, enabled will show.

Summary: After a restart, Enabled/Disabled text doesn't show in the menu. I have attached a video to demonstrate.
QA Contact: kglazko
Attached file gaia pull request
Attachment #8438733 - Flags: review?(21)
Assignee: nobody → ggoncalves
Target Milestone: --- → 2.0 S4 (20june)
blocking-b2g: --- → 2.0?
blocking-b2g: 2.0? → 2.0+
Comment on attachment 8438733 [details] [review]
gaia pull request

:arthurcc may be a better reviewer for this, we don't want to overwhelm :vintgetun.
Attachment #8438733 - Flags: review?(21) → review?(arthur.chen)
Comment on attachment 8438733 [details] [review]
gaia pull request

Thank you for the patch, Guilherme! As we were refactoring settings app using AMD pattern, could you write the newly added code an AMD module in root/ and include it in root/panel.js?

The module would take a dom element as the parameter and be enabled/disabled at the right time. Please refer to root/battery_item.js for details.
Attachment #8438733 - Flags: review?(arthur.chen)
Comment on attachment 8438733 [details] [review]
gaia pull request

Updated the PR. Thanks for the feedback, Arthur. Let me know if I missed anything!
Attachment #8438733 - Flags: review?(arthur.chen)
Comment on attachment 8438733 [details] [review]
gaia pull request

Looks much better! Please check my comments in github, thanks!
Attachment #8438733 - Flags: review?(arthur.chen)
Updated the PR to address the comments. I haven't changed the hidden element change because I was hoping to piggyback that fix in this bug (see my response on GitHub for details, please), but the other comments have been fixed.
Attachment #8438733 - Flags: review?(arthur.chen)
Comment on attachment 8438733 [details] [review]
gaia pull request

r=me, please squash the commits before merging, thanks.
Attachment #8438733 - Flags: review?(arthur.chen) → review+
Done, thank you!
Keywords: checkin-needed
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Needs uplifting..
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment on attachment 8438733 [details] [review]
gaia pull request

NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings.

[Approval Request Comment]
[Bug caused by] (feature/regressing bug #): 1022992
[User impact] if declined: Little impact, this is mostly UI polishing
[Testing completed]: Travis and manual.
[Risk to taking this patch] (and alternatives if risky): None.
[String changes made]: None.
Attachment #8438733 - Flags: approval-gaia-v2.0?(bbajaj)
No need to reopen, though.
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
I meant 2.0: 10729f6795fc6e4fad957e4e69d79a945323713c
Comment on attachment 8438733 [details] [review]
gaia pull request

Already landed in 2.0, cleaning the flag up..
Attachment #8438733 - Flags: approval-gaia-v2.0?(bbajaj) → approval-gaia-v2.0+
Issue does not repro, after restarting multiple times, "Enabled" is always shown on the Settings menu.

Environmental Variables:
Device: Flame 2.0
Build ID: 20140630000201
Gaia: c0c8ad187c0466285f2580531e09f8322996f561
Gecko: d4dc609bcc8a
Version: 32.0a2 (2.0)
Firmware Version: v122

User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Status: RESOLVED → VERIFIED
This issue has been verified successfully on Flame 2.1.

Steps:
1.Sign in Firefox account in Settings.
2.Restart device and check enabled text under 'Find My Device'.
** Enabled text under 'Find My Device' is shown.

Note: Restart device without the firefox account, The disabled text under 'Find My Device' is shown normally.
See attachment: Verify_Video_Flame2.1.MP4
Reproducing rate: 0/10

Flame v2.1 version:
Gaia-Rev        ccb49abe412c978a4045f0c75abff534372716c4
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/18fb67530b22
Build-ID        20141130001203
Version         34.0
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: