Tony Chung [:tchung] Reporter
	Description • 10 years ago

[Blocking Requested - why for this release]:

+++ This bug was initially created as a clone of Bug #1040829 +++

Instead of reopening the other bug, i'm going to file a new one since the behavior is a bit different.

If FMD setting is enabled, trying to toggle it will just turn off and back in.  It wont ever disable it.  

Logcat attached, and view the screencast here:  http://youtu.be/WrpOY6ieE6U


Repro
1) install 2.1 nightly on Open 2

Gaia-Rev        b3f9b97d16a1ab55f80239d63c1a85c3da3d39ad
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-aurora/rev/2c6e3261c47b
Build ID        20140921160204
Version         34.0a2
Device Name     ZTE_P821A20
FW-Release      4.3
FW-Incremental  eng.chencong.20140715.162404
FW-Date         Tue Jul 15 16:25:44 CST 2014

2) as part of FTU setup, enable fxAccounts and FMD
3) goto settings app > Find my device
4) tap the enable FMD button, and notice it never shuts off.  It just toggles off and quickly back on.

	KTucker [:KTucker][Inactive 3/4/2016]
	Comment 1 • 10 years ago

Adding qawanted here. Can we get this rechecked on all the applicable branches? Please also see bug 1058729

	Chris Kreinbring [:CKreinbring]
	Comment 2 • 10 years ago

Unable to repro on KK Flame 2.2 (engineering), Flame 2.2 (nightly), Flame 2.1 and Flame 2.0.
Actual result: When tapping the Find My Device switch to disable it, the password entry page appears.  After the user enters the correct password, the password entry page disappears and the FMD switch is disabled with no errors.

Flame 2.2 engineering
BuildID: 20140922125023
Gaia: e1fd99454b6cd5da4f2c58f928fc04c6d03f478f
Gecko: f4037194394e
Platform Version: 35.0a1
Firmware Version: V180
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0

Flame 2.2 nightly
BuildID: 20140922193018
Gaia: 3c898380b47f298cd3b7a0dacb3a6529e94322d4
Gecko: 790f41c631cc
Platform Version: 35.0a1
Firmware Version: Unknown
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0

Flame 2.1
BuildID: 20140922185144
Gaia: 3742913e11f69e789dcb0aa0dedf2e5572da0129
Gecko: df42b05782aa
Platform Version: 34.0a2
Firmware Version: V180
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Flame 2.0
BuildID: 20140923035745
Gaia: 6449cc35a8f0704d95acac374ba857bde4b86d6c
Gecko: b930730dba81
Platform Version: 32.0
Firmware Version: V180
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

	Joshua Mitchell (Inactive)
	Comment 3 • 10 years ago

clearing tracking  flags - this seems device specific to Open 2 so the flags should reflect that.

	Dietrich Ayala (:dietrich)
	Comment 4 • 10 years ago

Jared, can you take a look at the logcat? If there's something telling in there, we may need to block. Otherwise we need more testing to determine reproducibility on that device.

	Jared Hirsch [:jhirsch] (he/him) (Needinfo please)
	Comment 5 • 10 years ago

Hi Dietrich,

The attached logcat snippet doesn't tell us anything about why the observed behavior occurs.

However, there is another possible source of the bug: if you enable FMD using Firefox Account #1, then switch to Firefox Account #2, then try to disable FMD, it will fail. So, QA needs to reflash devices in order to test FMD with a different FxA test account. (See bug 1000323 for background on why FMD does this.)

Is it possible that the Open 2 is not being fully wiped between attempts? Could someone in QA verify that the bug still occurs on Open 2?

	Dietrich Ayala (:dietrich)
	Comment 6 • 10 years ago

Adding qawanted flag to answer comment #5.

	Joshua Mitchell (Inactive)
	Comment 7 • 10 years ago

Just a reminder - the QAnalysts lab (which has a dedicated QA-Wanted team) does not have Open 2 devices. Hopefully someone else sifting the QA-Wanted tag / queue can pick this one up.

	Tony Chung [:tchung] Reporter
	Comment 8 • 10 years ago

I'll qawanted this since i have the device

	Tony Chung [:tchung] Reporter
	Comment 9 • 10 years ago

i tried this again on a 2.1 build from today, and can;t reproduce this anymore.  going to clear nom on this for now, but leave it open when someone can see this.   it doesnt seem to be device specific.

	Norry.L.F(Leave from Mozilla)
	Comment 10 • 10 years ago

Hi,
    This issue still exit on Flame kk v2.0 and woodduck v2.0.

1.Fail rate:Once
2.Attach: logcat_flame_2037.txt and  logcat_woodduck.txt
3.Found time:20:37(flame)
-----------------------------
[Step]
1.Register a firefox account.
2.After you verify it, turn on the FWD.
3.Then tap it again to turn off first time.

[Expected Result]
The password box should pop up.

[Error]
The FWD turn off immediately, device does not pop up password box.
-------------------------------
Flame version:
Gaia-Rev        9c7dec14e058efef81f2267b724dad0850fc07e4
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/c17df9fe087d
Build-ID        20141019160201
Version         32.0
Device-Name     flame-kk
FW-Release      4.4.2
FW-Incremental  34
FW-Date         Tue Sep 30 14:06:36 CST 2014
Bootloader      L1TC00011840
---------------------------------------
Gaia-Rev        43d16612beb42ebfeb58a082155fdac2259d7191
Gecko-Rev       e7df4dde2d9dbedee942333d34eaea2afe32bebc
Build-ID        20141021095344
Version         32.0
Device-Name     soul35
FW-Release      4.4.2
FW-Incremental  1413855667
FW-Date         Tue Oct 21 09:41:33 CST 2014

	Jared Hirsch [:jhirsch] (he/him) (Needinfo please)
	Comment 14 • 10 years ago

(In reply to Norry.L.F from comment #10)
> 1.Register a firefox account.
> 2.After you verify it, turn on the FWD.
> 3.Then tap it again to turn off first time.
> 
> [Expected Result]
> The password box should pop up.
> 
> [Error]
> The FWD turn off immediately, device does not pop up password box.

Actually, the expected result is that FMD can be disabled. What you expect hasn't been implemented yet, see bug 1016496 for that ;-)

Seems like qawanted has conclusively shown that this bug can't be reproduced, closing. Tony, feel free to reopen if you can repro.