1100651 - Firefox Accounts login ends up stuck in empty dialog

Status: RESOLVED DUPLICATE of bug 1096603

(Firefox OS Graveyard :: FxA, defect)

Description

[:Harald Kirschner :digitarald]

Attachment: Empty Firefox Accounts dialog

Tested in Where Is My Water.

I was logged in successfully before using Firefox Accounts in another app.

Logging in causes an empty window with a next button and a small "Firefox Accounts" text in the top (see attachment). Tapping Next does nothing, I have to close the game. Starting the same flow again yields the same failure.

I tried logging the user out by injecting "navigator.mozId.logout()" but the behaviour persisted.

Comment 1

[:Harald Kirschner :digitarald]

Device Flame with v188 and 2.0

Build ID               20141114040205
Gaia Revision          1e300eac2e56d98ad51d414766d031db7d33221f
Gaia Date              2014-11-14 08:30:11
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/bbb68df450c2
Gecko Version          36.0a1
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  40
Firmware Date          Tue Oct 21 15:59:42 CST 2014
Bootloader             L1TC10011880

Comment 2

[:Harald Kirschner :digitarald]

Nick recommended ni? on Sam

Comment 3

[Sam Penrose]

A fix should land tomorrow.

Comment 4

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

Hmm. The parent bug, bug 1096603, was a regression not uplifted to the 2.0 or 2.1 branches.

Harald, the gaia revision you mentioned is not in the 2.0 branch, but it is in the 2.2 branch. I wonder if you were actually using the 2.2 (master) branch of gaia? If so, this is indeed a dupe of bug 1096603.

Can you please try again to reproduce the bug on v2.0 and confirm that it's fixed?

(In reply to Harald Kirschner :digitarald from comment #1)
> Gaia Revision          1e300eac2e56d98ad51d414766d031db7d33221f
> Gaia Date              2014-11-14 08:30:11

Comment 5

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

Ah, I don't think we need qawanted after all, since bug 1096603 comment 29 indicates that QA did not see the bug on 2.0.

Leaving this reopened until we get confirmation from Harald that WMW is working.

Comment 6

[:Harald Kirschner :digitarald]

Jaredm you are right. It seems like the device OTA updated to 2.2 :/ If Nick didn't see this behaviour on his 2.0, we can close this.