1025300 - FxOS v2.0 fails to login to Firefox accounts more than half of the time

Status: RESOLVED FIXED

(Firefox OS Graveyard :: FxA, defect)

Description

[Diego Wilson [:diego]]

Attachment: logcat.txt

I have been having trouble logging into Firefox Accounts in FxOS v2.0.

STR:

1. Go to settings -> Firefox Accounts
2. Tap on "create or sign in"
3. Enter existing verified account.

Result: the load screen lingers for half a minute then the age verification screen appears. Even though the account is already verified. I see some FirefoxAccounts errors in logcat which I attached.

Comment 1

[Diego Wilson [:diego]]

No-Jun,

Jared suggested I contact you to maybe try to reproduce this.

Comment 2

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

Refiling under gaia fxa component.

Diego, what kind of device are you using? What gecko/gaia build?

Comment 3

[No-Jun Park [:njpark]]

Hi, I'm using today's nightly build (2.0 Branch) on flame device, and I can't repro this using multiple verified accounts.  Perhaps the bug may be about the creation of the account that you were trying to use.  Did you try more than one verified account while reproducing this case?

Gaia      a6988c15b361938bea5976c846c147ecdc1121c0
Gecko     https://hg.mozilla.org/releases/mozilla-aurora/rev/52a276202888
BuildID   20140616000203
Version   32.0a2

Comment 4

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

Hey Diego - Can you still reproduce this bug? If so, it'd be great to get your gaia and gecko versions, as no-jun appended in the previous comment.

Anyway, about this line in the logcat:

I/Gecko   (  256): 76691793	FirefoxAccounts	ERROR	error POSTing /account/login: {"error":{},"message":null,"code":null,"errno":null}

This is funny. Normally, when a user enters an email, gecko calls /account/login to see if the account exists. The nulls are weird, though. They shouldn't be there.

I suspect this is a gecko bug, if anything. Maybe Sam has ideas around how to debug further, assuming this is still reproducible?

Comment 5

[Sam Penrose]

Jared I would rephrase your question this way: "if you can supply Sam with STR, he can debug in Gecko." These lines from the log:

I/Gecko   (  256): 76691793	FirefoxAccounts	ERROR	error POSTing /account/login: {"error":{},"message":null,"code":null,"errno":null}
I/Gecko   (  256): 76691795	FirefoxAccounts	ERROR	SERVER_ERROR

mean "services/fxaccounts/FxAccountsClient.jsm tried to make an HTTP POST to /account/login and failed somewhere inside the HTTP libs". I suspect we have either a non-FxA Gecko issue or a network connection problem. We could consider this a bug against handling random HTTP breakdowns. Without STR even if the root cause is at the FxA/HTTP junction in such a way that I could address it, I won't be able to.

Comment 6

[Diego Wilson [:diego]]

OK, I haven't been able to reproduce it Today. I'll close it for now and reopen if it resurfaces. Hopefully it was a temporary network prob. Thanks for the suggestions!

Comment 7

[Diego Wilson [:diego]]

Just as a side note. If this was indeed a networking issue, then there should be an error message. At least I'm pretty sure it shouldn't go into age verification for existing accounts.

Comment 8

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

Sounds great, Diego. Thanks for following up.

Comment 9

[toxborrow]

Hi Jared,

Would you confirm what the status is on this bug.  Sheila and I are double checking status and trying to clean up anything that is outstanding.

Cheers,
Tauni

Comment 10

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

Hey Tauni - This bug was set as unconfirmed, it hasn't been reproduced since the initial report, we are fine to ignore it. It's basically the same thing as closed.