Closed Bug 1577662 Opened 5 months ago Closed 4 months ago

Ensure profile reset doesn't connect sync after decoupling lands

Categories

(Firefox :: Firefox Accounts, defect, P1)

defect

Tracking

()

RESOLVED FIXED
Firefox 71
Tracking Status
firefox71 --- fixed

People

(Reporter: markh, Assigned: markh)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

A few years ago, in bug 1377200, we discovered that a profile reset/refresh would disconnect sync due to the preferences being reset. As we decouple sync and fxa we are likely to hit the same issue again. We need to work out what we can do to avoid this.

The priority flag is not set for this bug.
:markh, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(markh)

It turns out the bug will be the opposite - users signed in but not connected to sync will find themselves syncing after a reset.

Assignee: nobody → markh
Status: NEW → ASSIGNED
Flags: needinfo?(markh)
Priority: -- → P1
Summary: Ensure profile reset doesn't disconnect sync after decoupling lands → Ensure profile reset doesn't connect sync after decoupling lands

Gijs has some context around the decoupling work and also drew the short straw last time I touched this back in bug 1395332 - so apologies for drawing that straw again.

Pushed by mhammond@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d81fc0b39f4c
(part 1) - Allow profile refresh test to test multiple refresh scenarios. r=Gijs
https://hg.mozilla.org/integration/autoland/rev/90a414a9c39c
(part 2) - Profile reset now correctly handles that signed in to FxA doesn't always mean sync. r=Gijs
Status: ASSIGNED → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 71
You need to log in before you can comment on or make changes to this bug.