If the first sync client is unsynced and synced to another account, the second sync cliented synced to the first client will follow to the next account

RESOLVED INVALID

Status

Cloud Services
Firefox Sync: Backend
RESOLVED INVALID
6 years ago
6 years ago

People

(Reporter: nhirata, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

1. Nightly is synced to account A
2. Aurora is paired with Nightly
3. Nightly is unsynced 
4. Nightly gets set to an account B

Expected: Aurora is still synced to account A
Actual: Aurora is synced to account B

Note:
1. 1/23/2012 build for aurora
2. 2/08/2012 build for nightly
Can you clarify?

* Which product? Fennec, Firefox, ?
* When you say "unsynced", do you mean clicking "Deactivate This Device"?
* What makes you think that Aurora is now syncing with a different account?

If your answers are "Fennec", "Removing Sync account", and "I'm using Aurora and Nightly at the same time on the same Android device", then I'm afraid you're exercising an unsupported scenario, and this is pretty much expected.
(In reply to Richard Newman [:rnewman] from comment #1)

> * Which product? Fennec, Firefox, ?
Firefox Desktop Nightly, Firefox Desktop Aurora

> * When you say "unsynced", do you mean clicking "Deactivate This Device"?
"unlink this device"

> * What makes you think that Aurora is now syncing with a different account?
The header states that it's linked to the same account as the nightly for the email address.
Are you using different profiles for each browser? (I imagine so, but best to check.)

If you are, then I haven't the foggiest idea how this could occur. There's literally nothing that will exchange credentials between the two profiles in this way.

Can you reproduce this?
Component: General → Firefox Sync: Backend
QA Contact: general → sync-backend
Hrm.  I think it might be a profile mix up on my part.  I created 2 clean profiles with 1 clean sync account... and did not get this to happen again.  Closing off as invalid for now.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INVALID
Thanks for checking!
You need to log in before you can comment on or make changes to this bug.