1037522 - Unable to erase device from web using 2.0.0.0 prerelease user build

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: FindMyDevice, defect)

Description

[Peter deHaan [:pdehaan]]

### Push Done.
Gaia      18c44a1bc31b374ba00a069904465a8d07971a60
Gecko     https://hg.mozilla.org/releases/mozilla-aurora/rev/f880dae4fdbe
BuildID   20140711000201
Version   32.0a2
ro.build.version.incremental=eng.cltbld.20140513.082105
ro.build.date=Tue May 13 08:21:16 EDT 2014
B1TC300110F0


###Steps to reproduce:

1. Flash Flame phone using ./flash_pvt.py and choose:
    - 6) flame
    - 1) aurora
    - 1) User
    - 1) gaia + gecko

2. Go through the FTU flow.
    I set the timezone to "Los Angeles", "Mozilla Guest" wi-fi, don't create a FxA account, and then go to homescreen.

3. Unplug USB because, reasons.

4. Launch Settings app.

5. Go to "Find My Device" and create an FxA account.
    I create a brand new account through mailinator ([e-mail]), incrementing the date (07-11) each day.

6. Once the FxA account is set up and verified from Mailinator, you should see the "Enabled" toggle on the FMD settings page.

7. Log into https://find.firefox.com/ with the same account verified in earlier steps.
    For more better debugging, open your Developer tools and Console tab. Or start with the Network tab if you want to peep network traffic as well.

8. Test the Ring command to make sure your phone is talking to the server. Once you hear the blood curdling ringtone (2.0.0.0-prerelease) or the soothing jazz sounds (2.1.0.0-prerelease).

9. Sacrifice a goat.

10. Go back to the device and take a bunch of screenshots or something you can quickly verify that things are getting erased.

11. Press the Erase button on the website and agree to the confirmation button.

12. Wait for FTU process to initiate.


### Actual results:
My screenshots and photos are erased from my Gallery app. But I never get put into FTU flow.
I can see in my Network tab and Console in Developer tools that the {e:{}} command is sent.


### Expected results:
Kill it with fire, and then send me to FTU.


I have an SD card installed, but all other settings are default.

Comment 1

[Peter deHaan [:pdehaan]]

There are a lot of moving parts in this, sorry.

The TL;DR version was "format using ./flash_pvt.py, log in to FMD and erase from web" but then things get sticky when it comes to SD cards and other factors.
I can test other combinations if you want me to rerun this on my Flame without a SD card, or i can try a different SD card. Or i actually have two flames (one with 2.0 and one with 2.1). I can format the 2.1 flame w/ 2.0 to make sure it isnt a device specific thing...

Comment 2

[Marcia Knous [:marcia]]

Brogan was able to reproduce this issue this morning - see his results here: https://etherpad.mozilla.org/FMD-Testing-July11

Comment 3

[Peter deHaan [:pdehaan]]

Brogdan, what base image are you using?

```
$ adb shell getprop t2m.sw.version
```

Comment 4

[Marcia Knous [:marcia]]

Peter and Brogdan - As discussed at the meeting on Friday, can we please distill this down to a small set of STR? What I did in the other erase bug is try it with the erase command only first, and then tried it in combination with some of other things. https://docs.google.com/spreadsheets/d/1t-Mw7UgVh0zP-3RHfSiZO__96UaYYJceS95LmoAZI3w/edit#gid=0 is an example of what I used in the other bug, and I listed the parameters regarding flashing, base image, etc in the last comment of Bug 1037212#c11

Comment 5

[Brogan Zumwalt [Inactive]]

B1TC00011220
Which is v122, I believe

Comment 6

[Erin Lancaster [:elan]]

Looking at: https://docs.google.com/spreadsheets/d/1t-Mw7UgVh0zP-3RHfSiZO__96UaYYJceS95LmoAZI3w/edit#gid=0
I'd like to dupe this ticket to bug 1037212.

Comment 7

[Erin Lancaster [:elan]]

Can we confirm STR, asap? Thank you.

Comment 8

[Marcia Knous [:marcia]]

It looks as if when Brogan reproduced it these were the STR:

*Set up account on browser site then logged on to account on device, use find my device site to locate phone
**Result: FMD site locates phone successfully. Phone updated from yesterday's nightly using OTA update. Internal memory as default.

*Erase device using FMD site
**Result: https://bugzilla.mozilla.org/show_bug.cgi?id=1037522 - Phone updated  using flash script. Internal memory as default.

Comment 9

[Brogan Zumwalt [Inactive]]

Working with three team members both this week and last we are unable to find solid repro steps with more than 50 tests (each test with a reset of the phone and a new Firefox Account) showing only intermittent fails. 

The tests ran on Monday (not including those ran on Friday) include:

1. Launch Settings and navigate to Firefox accounts - Sign in to new or existing FxA and enable Find My Device - Log in to find.firefox.com with FxA account used on device - On find.firefox.com select Erase option and confirm - Result: Intermittant failures to erase device. Reproduced three times in a row on one device, then did not occur again using these STR's.
2. Launch Settings and navigate to Firefox accounts - Sign in to new or existing FxA and enable Find My Device - Log in to find.firefox.com with FxA account used on device - Ensure USB cord is NOT plugged into device - On find.firefox.com select Erase option and confirm - Result: Intermittant failures to erase device. Reproduced 2 times in a row on one device, then did not reproduce again using these STR's.
3. Launch Settings and navigate to Firefox accounts - Sign in to new or existing FxA and enable Find My Device - Log in to find.firefox.com with FxA account used on device - Ensure USB cord is NOT plugged into device and ADB debugging is NOT enabled - On find.firefox.com select Erase option and confirm - Result: Intermittant failures to erase device. Reproduced 6 times in a row on two devices, then did not reproduce again using these STR's.


Each of these cases were ran with variations that included: testing device locked with screen off, device locked with passcode, device unlocked, and device locked with screen on to attempt to find a way to get them to reproduce again. For Step 3 restarted adb mode in TCP and attempted to grab logcat over WiFi, but issue no longer reproduced at this point.

Was unable to get logcat of this issue reproducing. Was unable to find STR's for this bug.

Environmental Variables:
Device: Flame 2.0 (273mb)
Build ID: 20140714000202
Gaia: ca022f811bcbbda0f89086094a9e92bb220fea18
Gecko: 376889ab0e02
Version: 32.0a2 (2.0) 
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Comment 10

[Marcia Knous [:marcia]]

If all things were equal in Comment 9, these intermittent failures are a bit concerning even if we don't have exact STR. So I read from Comment 9 it failed 11 times in the 50 times they tried it - that is about a 22% failure rate if I did the math correct.

Comment 11

[Tony Chung [:tchung]]

erase feature not working consistently is a feature blocker.

Comment 12

[Peter deHaan [:pdehaan]]

Current status with today's User 2.0 builds.

STR:
0. Flash phone
1. Complete FTU
2. Create Firefox Account on device and verify
3. Sign in to find.firefox.com
4. Click erase button.
5. Wait.

test 1: [e-mail]
- SIM
- SD Card
- located on map
- ringer rings
- lock locks (and sets lock code)
- erase erased
= TL;DR: Device erased screenshots and triggered FTU.

test 2: [e-mail]
- NO SIM CARD
- SD Card
- located on map
- ringer rings
- lock locks (and sets lock code)
- erase erased
= TL;DR: Device erased screenshots and triggered FTU.

test 3: [e-mail]
- NO SIM CARD
- NO SD CARD
- located on map
- ringer rings
- lock locks (and sets lock code)
- erase erased
= TL;DR: Device erased screenshots and triggered FTU.

test 4: [e-mail]
- SIM CARD
- NO SD CARD
- located on map
- ringer rings
- lock locks (and sets lock code)
- erase erased
= TL;DR: Device erased screenshots and triggered FTU.

I'm happy to close this out as "WORKSFORME". If Bogdan and team are still seeing issues for them, we file a new bug with their specific repro steps. (I'm not touching custom ringtones or music or apps or anything else).

Comment 13

[Peter deHaan [:pdehaan]]

:elan, I wouldnt dupe to bug 1037212 since that specifically mentions ringtones and music, which was a different flow than I was doing. I vote for closing as "WORKSFORME" or "FIXED", and :BroganZ can file a new bug with their specific repro steps or we can just track :marcia's bug if they're seeing her issue.

Comment 14

[Marcia Knous [:marcia]]

This wouldn't be resolved fixed since nothing was done to fix the bug - the right status is WFM.