Closed Bug 1059411 Opened 10 years ago Closed 10 years ago

[Settings][FxA] Error 'Unable to connect' while signing up to Firefox Accounts

Categories

(Firefox OS Graveyard :: FxA, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v2.0 unaffected, b2g-v2.1 affected)

RESOLVED WORKSFORME
Tracking Status
b2g-v2.0 --- unaffected
b2g-v2.1 --- affected

People

(Reporter: jschmitt, Unassigned)

Details

(Keywords: regression)

Attachments

(2 files)

Attached image FXA.png
Description: After signing out a previous account, FXA shows an error 'unable to connect' when signing up a new account. Repro Steps: 1) Update a Flame to 20140827040203 2) Connect to a Data/Wifi network 3) Open Settings > Firefox Accounts 4) Sign up with a new email and verify the account 5) Open Settings > Firefox accounts 6) Sign out the account 7) With a new email sign up for Firefox Accounts Actual: An error message 'unable to connect' is displayed. Expected: There is no error message when trying to sign up another account. Environmental Variables: Device: Flame Master 319MB Build ID: 20140827040203 Gaia: 6e804a42ab90f4251c7fe8c68731dc1c6abd8006 Gecko: 0753f7b93ab7 Version: 34.0a1 (Master) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Notes: Repro frequency: 60% See attached: screenshot and logcat
Attached file log.txt
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Issue does not occur on 2.0 Environmental Variables: Device: Flame 2.0 319MB Build ID: 20140827000204 Gaia: d72f8ad53448aed577c01ff6e11d958463f261e7 Gecko: 2a18149b3ae8 Version: 32.0 (2.0) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
[Blocking Requested - why for this release]: regression in a major feature. Requesting a window.
blocking-b2g: --- → 2.1?
QA Whiteboard: [QAnalyst-Triage?]
Component: Gaia::Settings → FxA
Flags: needinfo?(pbylenga)
Some possible additional steps are needed to repro this bug: 1. Sign into a new account and verify the email 2. Sign out of account 3. Sign into a pre-existing account
With the new findings, I am not able to repro on 2.0 Flame 319MB Environmental Variables: Device: Flame 2.0 319MB Build ID: 20140827000204 Gaia: d72f8ad53448aed577c01ff6e11d958463f261e7 Gecko: 2a18149b3ae8 Version: 32.0 (2.0) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Flags: needinfo?(pbylenga)
Flags: needinfo?(pbylenga)
Flags: needinfo?(rpappalardo)
jr mentioned in IRC that this behavior is likely still expected if you sign into a device with one account and then try to use another account on the same device.
I've also seen that behavior when testing with different accounts. Firefox Accounts doesn't handle this well (yet), though switching back and forth between different accounts probably isn't the most common scenario.
Flags: needinfo?(rpappalardo)
(In reply to Marcia Knous [:marcia - use needinfo] from comment #6) > jr mentioned in IRC that this behavior is likely still expected if you sign > into a device with one account and then try to use another account on the > same device. Maybe JR thought you were referring to FMD. This is definitely not an expected bug for Firefox Accounts.
Hey Richard, Interesting, I've never seen this bug, and I do a lot of new/old account swapping as part of daily development. Do you have any hints around what kind of behavior reproduces this bug? Maybe there's some flow I very rarely exercise when I'm developing, so I've never seen it. Jared
Flags: needinfo?(rpappalardo)
I was unable to reproduce this issue on the original reporters build after 5 attempts each with comment 0 and comment 4 steps. Leaving regression tags so others can attempt. Environmental Variables: Device: Flame Master BuildID: 20140827040203 Gaia: 6e804a42ab90f4251c7fe8c68731dc1c6abd8006 Gecko: 0753f7b93ab7 Version: 34.0a1 (Master) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
I haven't done this for awhile, but I recall we were doing a lot flashing, going through FTU flow, creating and removing users, etc. That black screen will definitely appear with poor wifi signal, but I'm less likely to pin this to FxA and neither No-Jun nor I can repro on 2.1 either.
Flags: needinfo?(rpappalardo)
Multiple parties have been unable to reproduce this in the latest - closing as WFM, please reopen if this pops back up soon.
Status: NEW → RESOLVED
blocking-b2g: 2.1? → ---
Closed: 10 years ago
QA Whiteboard: [QAnalyst-Triage+]
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: