1014266 - Rejection errors in FxA

Status: RESOLVED DUPLICATE of bug 1195569

(Firefox :: Sync, defect)

Description

[Richard Newman [:rnewman]]

This is indicative of something really weird.

User found my on IRC. Fresh profile, signed in, no sync data. (Indeed, no sync log output at all.)

This was repeated on a fresh profile again.

Here's the console output:

 promise chain failed to handle a rejection.
 
Date: Wed May 21 2014 23:08:17 GMT+0100 (BST (Britisk normaltid))
Full Message: no user is logged in
Full Stack: JS frame :: resource://gre/modules/services-sync/browserid_identity.js :: this.BrowserIDManager.prototype.initializeWithCurrentIdentity/< :: line 196
JS frame :: resource://gre/modules/Promise.jsm :: Handler.prototype.process :: line 767
JS frame :: resource://gre/modules/Promise.jsm :: this.PromiseWalker.walkerLoop :: line 531
native frame :: <unknown filename> :: <TOP_LEVEL> :: line 0
A promise chain failed to handle a rejection.


Date: Wed May 21 2014 23:08:17 GMT+0100 (BST (Britisk normaltid))
Full Message: Error: A different user signed in
Full Stack: AccountState.prototype.resolve@resource://gre/modules/FxAccounts.jsm:183
AccountState.prototype.getUserAccountData/<@resource://gre/modules/FxAccounts.jsm:113
Handler.prototype.process@resource://gre/modules/Promise.jsm:770
this.PromiseWalker.walkerLoop@resource://gre/modules/Promise.jsm:531
 FxAccounts.jsm:183

Comment 1

[Richard Newman [:rnewman]]

Perhaps relevant:

Bug 992363

Comment 2

[Richard Newman [:rnewman]]

"Btw, I don't know if this is relevant, but in the manage account thingy, it says "You are logged in as: [e-mail] [e-mail]" reapeating my email twice. Just a weird thing that might be worth mentioning."

Comment 3

[Chris Karlof [:ckarlof]]

(In reply to Richard Newman [:rnewman] from comment #2)
> "Btw, I don't know if this is relevant, but in the manage account thingy, it
> says "You are logged in as: [e-mail] [e-mail]" reapeating my
> email twice. Just a weird thing that might be worth mentioning."

What locale? That's a side of effect of some unfortunate translation timing, but should get resolved in the next release.

Comment 4

[Chris Karlof [:ckarlof]]

The user unfortunately reformatted his HD, and then reset his password, which of course makes the old sync data unrecoverable. He was remarkably pleasant about it. I filed the below bug to at least help provide a warning during the password reset process about the consequences on your sync data:

https://github.com/mozilla/fxa-content-server/issues/1148

Comment 5

[Richard Newman [:rnewman]]

(In reply to Chris Karlof [:ckarlof] from comment #3)

> What locale? That's a side of effect of some unfortunate translation timing,
> but should get resolved in the next release.

Norwegian, for the record.

Comment 6

[Richard Newman [:rnewman]]

Shouldn't we be doing something to (a) make sure these errors are handled, if Bug 992363 didn't take care of that, and (b) getting the client into a usable state? Not sure why this is RESOLVED INVALID.

Or do we already have a bug on file that we can dupe this to?

Comment 7

[Mark Hammond [:markh] [:mhammond]]

(In reply to Richard Newman [:rnewman] from comment #6)
> Shouldn't we be doing something to (a) make sure these errors are handled,
> if Bug 992363 didn't take care of that,

Those rejection message fixes didn't make it to 29, but that's not a big deal IMO - it's noise in the logs, but shouldn't have any visible impact to the users.

> (b) getting the client into a
> usable state? Not sure why this is RESOLVED INVALID.

It's not clear to me that the logs aren't accurate - that at some point the user logged out.  One followup might be to ensure that when the user is in this state we still get logs, which doesn't seem to be the case.  I don't see any other evidence of things not being usable (other than the fact the user lost all their data :(

Comment 8

[Chris Karlof [:ckarlof]]

I can re-open for the un-handled rejections, but as markh says, I think they are just noise and there is no suggestion they are causing problems.

> Fresh profile, signed in, no sync data.

This user didn't have sync data because I determined via an irc conversation that he reset his password, which clears his server sync data.

Comment 9

[Mark Hammond [:markh] [:mhammond]]

We still occasionally see "Error: A different user signed in", but never repeated. That's being tracked in bug 1195569, so I'm closing this as a dupe of that.