Closed Bug 1211705 Opened 4 years ago Closed 2 years ago

The user will be stuck in the FTU if they cancel while importing Gmail contacts and then try again

Categories

(Firefox OS Graveyard :: Gaia::First Time Experience, defect, P2)

ARM
Gonk (Firefox OS)
defect

Tracking

(b2g-v2.2 affected, b2g-master affected)

RESOLVED WONTFIX
Tracking Status
b2g-v2.2 --- affected
b2g-master --- affected

People

(Reporter: KTucker, Unassigned)

References

()

Details

(Whiteboard: [2.5-Daily-Testing][Spark][Systemsfe])

Attachments

(1 file)

Attached file GmailStuckonFTU
If the user tries to import contacts from a Gmail account that has no contacts, cancels the import and then tries again, they will be stuck on the "No friends or contacts found in this account" screen. The user will have to reboot their phone to recover.

Repro Steps:
1) Update a Aries to 20151005111147
2) Flash or factory reset the device.
3) Turn on data and keep tapping "Next" during the FTU until reaching the "Import contacts" screen.
4) Tap on "Gmail" and when prompted login to an account that has not contacts associated with it.
5) Give permission when prompted and tap "OK" on the "No friends or contacts found in this account" screen.
6) Tap on "Gmail" again and tap "Cancel" while it is connecting to the friends list. 
7) Tap on "Gmail" again and then tap "OK" when prompted "No friends or contacts found in this account". 

Actual:
The user will be stuck on the "No friends or contacts found in this account" screen and will have to restart their device to recover.

Expected:
The user is not stuck on the "No friends or contacts found in this account" screen. and is taken back to the "Import contacts" screen after tapping "OK". 

Notes:

Environmental Variables:
Device: Aries 2.5
Build ID: 20151005111147
Gaia: b994cedaa7ef9bfadcbe841601d9dc8d2e5379f9
Gecko: 45f01961ecd0ad9a45067f3e08bfb92539042eeb
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 44.0a1 (2.5)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0

Repro frequency: 5/5 100%
See attached: video clip, logcat
This also occurs on the Flame 2.5 and Flame 2.2

The user can get stuck on the "No friends or contacts found in this account" screen.

Device: Flame 2.5
Build ID: 20151002030232
Gaia: 9a682cb7bc8b7fde624a9b2b3c2d64415a08b04b
Gecko: 5f16c6c2b969f70e8da10ee34853246d593af412
Gonk: c4779d6da0f85894b1f78f0351b43f2949e8decd
Version: 44.0a1 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0

Device: Flame 2.2
BuildID: 20151005032502
Gaia: 5dd95cfb9f1d6501ce0e34414596ef3dd9c2f583
Gecko: 2ab95b3d02a7
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 37.0 (2.2) 
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
Whiteboard: [2.5-Daily-Testing][Spark]
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmercado)
Whiteboard: [2.5-Daily-Testing][Spark] → [2.5-Daily-Testing][Spark][Systemsfe]
Alison this issue is bad if it occurs, but the steps are really reaching making me think this is more of a tester bug.  Would you block on this?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmercado) → needinfo?(ashiue)
This is a bit of a corner case - to have a gmail account with 0 contacts and also to attempt to import those contacts. but it does point at a real logic problem in the FTU so we should keep it around. I wonder if it was fallout from the work around import services when we removed facebook contacts import. Flagging qawanted - I would like to know if this is a regression. I don't think we necessarily need a full window, but it would be useful to know if this reproduces on v2.2
Keywords: qawanted
Priority: -- → P2
Comment 1 says this reproduces on 2.2.
Flags: needinfo?(jmercado)
Keywords: qawanted
Flags: needinfo?(jmercado)
This is really a bug needs to be fixed but not a blocker issue.
Flags: needinfo?(ashiue)
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.