Closed Bug 709332 Opened 13 years ago Closed 12 years ago

Node reassignment: handle 401s for credential errors by marking sync as failed

Categories

(Firefox for Android Graveyard :: Android Sync, defect, P1)

All
Android
defect

Tracking

(fennec+)

RESOLVED DUPLICATE of bug 709329
Tracking Status
fennec + ---

People

(Reporter: ally, Assigned: nalexander)

References

Details

      No description provided.
Assignee: nobody → rnewman
OS: Mac OS X → Android
Hardware: x86 → All
tracking-fennec: --- → ?
tracking-fennec: ? → +
Assignee: rnewman → nalexander
Bug 709329 should handle this case.  What is intended to happen is that the 401 comes and we make a note that the cluster URL is stale before aborting the sync.

The note short circuits the usual sync delay and we sync as soon as we are asked (usually about 30 seconds, system dependent).

The note also asks for a new cluster URL, at which point we'll discover that the user's password has changed.  The sync is aborted, and this should show up in the Android Settings->Sync UI (on my Transformer Prime, get a "red resync button"). 

At this time, there is no additional UI for announcing this to the user.  Do we need a follow-on ticket for password change?

I don't have a way to introduce 401's, so haven't tested live -- any advice appreciated.

TL;DR -- fixed by 709329.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Product: Mozilla Services → Android Background Services
Product: Android Background Services → Firefox for Android
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.