Closed Bug 1091186 (migratesyncandroid) Opened 6 years ago Closed 5 years ago
[meta] Offer Firefox Accounts to existing Android Sync users
This is the Android tracking bug parallel to Bug 999910. This ticket tracks implementing: * Sync protocol deprecation indicators (which apply to both Sync 1.1 and Sync 1.5 clients); * automatically upgrading to a Firefox Account when the appropriate sentinel is found on the Sync 1.1 server. That is, this ticket tracks semi-gracefully handling a Sync service endpoint being de-commissioned, and being a *second* device upgraded in a constellation of devices. It does not track being the *first* device upgraded.
Bug 956444 tracks the first parts of this (handling protocol deprecation indicators).
Depends on: 956444
Bug 1091189 tracks the second parts of this (reacting to uploaded Firefox Account sentinels).
Some time after the real work of this ticket is done, we can move on to Bug 957845, which tracks removing the old Android Sync account type from Fennec entirely.
Depends on: 957845
(In reply to Nick Alexander :nalexander from comment #1) > Bug 956444 tracks the first parts of this (handling protocol deprecation > indicators). It looks like rnewman has already done quite a bit of work in this direction, and Bug 895526 and Bug 908464 track the work for the first parts of this. I think Bug 956444 actually tracks the second parts of this, and my Bug 1091189 duplicates Bug 956444; but I'm waiting for rnewman's confirmation.
Component: Firefox Sync: Cross-client → Android Sync
Product: Mozilla Services → Android Background Services
Hi Nick, is there remaining useful to track in this bug tree or should we just close it out? I'm trying to make sure we've got a clean tree in prepararation for sync1.1 decomission.
(In reply to Ryan Kelly [:rfkelly] from comment #5) > Hi Nick, is there remaining useful to track in this bug tree or should we > just close it out? I'm trying to make sure we've got a clean tree in > prepararation for sync1.1 decomission. Close it out. We'll re-open for fall-out.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.