Closed Bug 709393 Opened 13 years ago Closed 10 years ago

Handle 401s for credential errors by prompting for new credentials

Categories

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

Product:
Firefox for Android Graveyard
Component:
Android Sync
Platform:
All
Android
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: ally, Unassigned)

References

Details

      No description provided.
I think we can flag the SyncResult with an auth error, but we'll see when we get to this.
OS: Mac OS X → Android
Hardware: x86 → All
Summary: * Handle 401s for credential errors by prompting for new credentials needed. → Handle 401s for credential errors by prompting for new credentials
Target Milestone: --- → Future
resetting your password on desktop and attempting to sync will trigger this.
Priority: -- → P2
This will likely need new strings, will we be able to add those in despite string freeze? Ally mentioned possibly piggybacking on AMO string changes, if that happens.
Depends on: 705767
AFAIK late-l10n isn't impossible, just undesirable. But whether we'll need that or not depends on whether this will be landing "late" in whatever cycle it's landing in, right?
I'd think that this would need to a bad blocker to take strings for 11. There's also no AMO piggyback that I'd know of. Yet?
Priority: P2 → P1
Target Milestone: Future → ---
Product: Mozilla Services → Android Background Services
Depends on: 963442
Priority: P1 → --
We have this in place for FxAccounts + Sync 1.5 (via, I suppose, Bug 951304 and a long list of follow-ups).  We're not going to implement anything like this for Sync 1.1.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
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.