Closed Bug 1067702 Opened 10 years ago Closed 8 years ago

FxA auth fails to recover after prolonged sync server outage?

Categories

(Firefox :: Sync, defect, P2)

Product:
Firefox
Component:
Sync
Type:
defect
Points:
3

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1071786

People

(Reporter: rfkelly, Unassigned)

References

Details

Bug 1067533 contains some interesting logs, and may point to an incorrect corner-case code path in the sync fxa authentication logic.  I'm filing this as a follow-up bug to dig in and see if there's any issues there.

Briefly: the user got sync failures for a while due to server trouble, but then kept seeing failures even after the server was up and working again.  Sync client logs claim a failure to auth with message "No keyFetchToken" but don't seem to indicate any attempt to re-authenticate or to surface any actionable message to the user.
Flags: qe-verify+
Whiteboard: [qa+]
FWIW we've had at least one other report of Bug-1067533-like symptoms from a user in IRC.  Given the rocky week we had with 503s recently, there are probably more than a few users stuck in this state :-(
Bug 1071786 may partially explain failure to recover from this state.
Depends on: 1071786
Points: --- → 3
Flags: firefox-backlog+
Whiteboard: [qa+]
Priority: -- → P2
Given the lack of actionable info here I'm calling this a dup of bug 1067702.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Oops, I meant (In reply to Chris Karlof [:ckarlof] from comment #4)
> Given the lack of actionable info here I'm calling this a dup of bug 1067702.
> 
> *** This bug has been marked as a duplicate of bug 1071786 ***

Obviously, I meant bug 1071786. :)
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in before you can comment on or make changes to this bug.