Closed Bug 1014078 Opened 10 years ago Closed 10 years ago

setting up sync with a new profile caused dataloss in original profile

Categories

(Firefox :: Sync, defect)

x86
macOS
defect
Not set
normal

Tracking

()

VERIFIED INCOMPLETE

People

(Reporter: guigs, Unassigned)

Details

(Whiteboard: [qa+])

Reference story: [https://support.mozilla.org/en-US/questions/1001188?utm_campaign=questions-reply&utm_medium=email&utm_source=notification]

Description: When a user sets up a profile with a new profile, the second computer or device profile is overwritten. A functionality in the previous sync did a check to what to do: merge the profile, overwrite etc. Incorporating this or a warning to a new user may prevent some of this misunderstanding. 

I will also add this to the new sync kb in support.
The default behavior should be to "merge" the data, not overwrite. The user in that support thread is must be experiencing a bug of some sort - perhaps we should morph this bug to cover that. Would they be able to comment here to provide more information and potentially provide Sync logs?

(Bug 966530 covers the fact that we no longer offer different options, but that shouldn't result in any data loss.)
Component: Sync → Firefox Sync: Backend
Product: Firefox → Mozilla Services
Summary: [User story] Request to add a warning when syncing a profile to an account with nothing → setting up sync with a new profile caused dataloss in original profile
Version: 29 Branch → unspecified
I can't reproduce this (which isn't surprising really - if this was happening in all cases I believe we would have noticed it).

My test was simply:

1) On one profile, add a bookmark, then setup sync, and wait for sync to complete.
2) On second profile, add a different bookmark, setup sync and wait for sync to complete.  Verify new bookmark *and* original bookmark from (1) now exists.
3) Back to first profile, sync.  Ensure both bookmarks exist.

Richard, can you think of anything that might force sync to get into the state where one of the profiles is clobbered?
I commented in the support thread, but: no, it's pretty unlikely that Sync was involved here.
Whiteboard: [qa+]
Going to close this since it doesn't seem actionable without more info.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
ok
Status: RESOLVED → VERIFIED
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in before you can comment on or make changes to this bug.