1026603 - [B2G][FxA][FTE] Losing wifi while signing into a Firefox Account in FTE can block user progression

Status: RESOLVED DUPLICATE of bug 998464

(Firefox OS Graveyard :: FxA, defect)

Description

[Eric Kramer [:Kramer]]

Attachment: Logcat_FxA_Wifi

Description:
Phone becomes locked into a "Connecting" state when wifi is lost during the password section of Firefox Account creation in the FTE. This issue can only be reversed by restarting the device. 

*Note: Issue DOES reproduce via Firefox Account creation in Settings. However, User can get off the "Connecting" screen in this scenario.

Prerequisite:
This bug is easier to reproduce with a dedicated router.

Repro Steps:
1) Update a Flame to 20140616000203
2) Proceed through FTE until "Select a Network"
3) Sign in to a network (preferably a dedicated router that you can unplug later)
4) Proceed through FTE until Firefox Accounts
5) Create a new account
6) Enter a password
7) Disconnect the router (losing the wifi connection)


Actual:
The phone goes into a "Connecting" state and cannot drop out of it. 


Expected:
There is a "no connection" splash screen explaining to the user that something happened to their connection.

Environmental Variables:
Device: Flame 2.0
Build ID: 20140616000203
Gaia: a6988c15b361938bea5976c846c147ecdc1121c0
Gecko: 52a276202888
Version: 32.0a2 (2.0) 
Firmware Version: v121-2

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


Repro frequency: (4/5, 80%)
Link to failed test case: https://moztrap.mozilla.org/manage/case/12860/ 
See attached: (video clip, logcat)

============================================================================
This issue DOES reproduce on the following:

Flame
2.1
Environmental Variables:
Device: Flame Master
Build ID: 20140616040202
Gaia: dfc4703bb81d1fa4f2087a1a6124b47a80a5d1de
Gecko: 80431d4fd0da
Version: 33.0a1 (Master) 
Firmware Version: v121-2

----------------------------------------------------------------------------
Buri
2.1
Device: Buri Master
Build ID: 20140611040203
Gaia: 0750f66a0004870773c9a743fa6bdbe124379336
Gecko: 18c21532848a
Version: 33.0a1 (Master) 
Firmware Version: v1.2device.cfg

2.0
Environmental Variables:
Device: Buri 2.0
Build ID: 20140616144242
Gaia: 0f254c92bc44d614ae56a855f18a895a7e4703ad
Gecko: 874608951fc8
Version: 32.0a2 (2.0) 
Firmware Version: v1.2device.cfg

----------------------------------------------------------------------------
Open_C
2.0
Environmental Variables:
Device: Open_C 2.0
Build ID: 20140613082917
Gaia: 5b1fdc6000d35962769e789b924b24e166a27759
Gecko: 8415553664fd
Version: 32.0a2 (2.0) 
Firmware Version: P821A10V1.0.0B06_LOG_DL

============================================================================
This issue does NOT reproduce on the following:

Flame (no Firefox Account setup in FTE)
1.4
Environmental Variables:
Device: Flame 1.4
Build ID: 20140616000202
Gaia: 164644d91290708a71436dfdf4301e33b92e2c77
Gecko: 2949e8bef869
Version: 30.0 (1.4) 
Firmware Version: v121-2

Buri (no Firefox Account setup in FTE)
1.3
Environmental Variables:
Device: Buri 1.3
Build ID: 20140613084813
Gaia: 8d6bd6c484557c5322bf14798a4273d2a8f4300f
Gecko: 634b8bb42eea
Version: 28.0 (1.3) 
Firmware Version: v1.2device.cfg

Comment 1

[KTucker [:KTucker][Inactive 3/4/2016]]

This should have been checked on Open C 2.1 and you need to state what the actual result is for each device. Also, your divider lines are confusing.

Comment 2

[Eric Kramer [:Kramer]]

This issue shows the same result on all devices that repro. 

This issue DOES reproduce on Open_C 2.1
Device: Open_C Master
Build ID: 20140617040203
Gaia: eac13407742a55b11e1877b4df2abdfd22cd582e
Gecko: bb35d1b73634
Version: 33.0a1 (Master) 
Firmware Version: P821A10V1.0.0B06_LOG_DL

Result:
The device goes into a "Connecting" state and the User cannot drop out of it. This requires a restart in the FTE.

Comment 3

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

Marking as a dupe of bug 998464. If that bug needs to block 2.0, please flag it as such.

Comment 4

[bhavana bajaj [:bajaj]]

This seems very edge casey to me especially doing step 3. Can QA confirm if there is ever a point in FTE to reproduce this without ever connecting to the network from the beginning ? IF that is the case this becomes more of a bug we should fix as there may be cases in several regions that folks may go through FTE without Wifi/cell data and if you have to restart the phone  during that, its bad!

Comment 5

[Eric Kramer [:Kramer]]

This issue does NOT repro if the user never connects to a network.

If the user is not connected to a network they will see a "Unable to Connect" screen when trying to create a new account / sign in. They are unable to get to the password input screen.

Comment 6

[Joshua Mitchell (Inactive)]

This issue has been marked resolved - Dupe.