Closed Bug 739629 Opened 8 years ago Closed 8 years ago

Expose safe account creation API for profile migration

Categories

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

ARM
Android
defect

Tracking

()

VERIFIED FIXED
mozilla14
Tracking Status
firefox13 --- affected
blocking-fennec1.0 --- beta+

People

(Reporter: rnewman, Assigned: nalexander)

References

Details

(Whiteboard: [sync])

+++ This bug was initially created as a clone of Bug #734211 +++

This will largely entail lifting AccountActivity.createAccount and adding validation, and documenting its assumptions (e.g., about threading).

Also will need an option to ensure that no account already exists, to avoid ending up with two!

**DONE**: While we're here, we can also add a little API to check whether a Sync account exists, and strip that logic out of the main Fennec code.
This sounds like scope creep pre-1.0 release.  I see this isn't marked as a blocker.  Are we being careful not to add more features this late in the game?
(In reply to Damon Sicore (:damons) from comment #1)
> This sounds like scope creep pre-1.0 release.  I see this isn't marked as a
> blocker.

It blocks a blocker: Bug 715550.

> Are we being careful not to add more features this late in the
> game?

Broadly, yes. Bug 715550 is a long-standing feature item. This bug is only so much younger because it was forked off Bug 734211 to avoid multi-part nonsense.

Without this bug, a XUL Fennec user with Sync set up will lose their Sync settings. With this bug (and Bug 715550, of course) they'll be silently migrated to Android Sync and receive continuity of service.

If that's considered too risky or schedule-affecting for Beta, then please re-triage Bug 715550, and we'll adjust the priority for this accordingly.
blocking-fennec1.0: --- → ?
Delaying bugs related to profile migration past beta means they will be released with essentially 0 testing. Delaying them past release is effectively WONTFIX-ing them.
blocking-fennec1.0: ? → beta+
Whiteboard: [sync]
Assignee: nobody → ally
What is the status here? Can we get someone assigned to work on this bug?
Assignee: ally → nalexander
See https://bugzilla.mozilla.org/show_bug.cgi?id=715550#c2 for details.
Status: NEW → ASSIGNED
First draft review done. Waiting on review changes to reflect migration of client ID/name as well as account details.
https://hg.mozilla.org/mozilla-central/rev/190a237b1456
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Product: Mozilla Services → Android Background Services
Product: Android Background Services → Firefox for Android
You need to log in before you can comment on or make changes to this bug.