Closed Bug 1346792 Opened 7 years ago Closed 7 years ago

After sync with old build, bookmark order is broken everyday

Categories

(Firefox :: Sync, defect)

All
Windows
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1353641
Tracking Status
firefox55 --- affected

People

(Reporter: masayuki, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

Attachments

(2 files)

I have a lot of VM environment which are installed Nightly at using for tests and added to my sync for testing smoother.

In the last week, I used some builds in such environments, and the Nightly builds are not updated for long time. After that, the order of my bookmark in my main environment is broken every time when I leave from my desk.

Even after I restore bookmarks from the backup, the order is broken again and again... Even after I changed the order correctly, the order is broken again and again too.

So, it seems that restoring bookmark order with my hand or from backup file isn't respected than the cloud data. I guess, the items' modify time are not updated at restoring or changing the order by my hand.

I hope that changing something of bookmark should cause giving higher priority than the cloud data.
> I hope that changing something of bookmark should cause giving higher priority than the cloud data.

Yes, it definitely should.

Is there any chance you can replicate this and get us logs describing it? It seems surprising that it would happen every time (it's less surprising that bookmark restore causes some problems, until bug 1230011 is resolved at least, although restoring by hand should not have these issues).

This describes how to get the logs https://wiki.mozilla.org/CloudServices/Sync/File_a_desktop_bug, but you might need to turn on success logging (which is described there also), if there are no error logs, which seems possible from your description. Unless trace logging is enabled there shouldn't be PII in the log files, but of course feel free to mark as moco confidential if you're concerned.
Flags: needinfo?(masayuki)
I replaced my folder names, bookmark item names and bookmark URLs in this file with different string. So, not including my privacy.

Note that there is another log file which includes more folder and bookmark item sync log. However, it's hard to hard my privacy from it due to too many items. But if you need it, I'll try to attach it too.
Flags: needinfo?(masayuki)
Oh, I realized that currently, broken order of folders in bookmark toolbar is same as its order on Android. So, my restored bookmarks on desktop is now overwritten with *older* bookmark of Android's.
From triage: markh to follow up
Flags: needinfo?(markh)
Now, my bookmark was synced from the cloud immediately after restoring bookmark from a JSON file. The log is here. I'm surprised at the restored data is judged as older than the cloud date immediately after restoring the bookmark...
Depends on: 1124369, 1324503
Oh, I experienced odd symptom about this issue:

1-1. Backed up bookmark on my Windows PC (when the bookmark order is correct).
1-2. Tried to restore bookmark on another Windows PC from the backup.

Then, I see an error message, "Unable to process the backup file.", which is bookmarksRestoreParseError. And the bookmark becomes empty on the second PC and on my Android device after sync. However, oddly, the bookmark in the first PC won't become empty. Then,

2-1. Tried to restore bookmark on the first PC again.
2-2. Synced it on the others (both the second PC and the Android device).

Then, I see broken order bookmarks on them. Finally,

3-1. Sorted the bookmark on the *second* PC by my hand.
3-2. Synced it from the second machine and then, synced on the other devices.

On the *first* PC, the bookmark order becomes same as the second PC. However, Android's bookmark order is still different from desktop PCs'.

4-1. Synced on the both PCs again later.

Then, the bookmark order becomes same as Android's. So, looks like that the cloud data is overwritten with Firefox for Android.
See Also: → 1352233
Given Android seems involved and bug 1352947 demonstrates that Android sometimes writes folder records with missing children, and given we know that may cause desktop to do strange things to the bookmark order, I think we should wait for (IOW, blame) bug 1352947. I also suspect that bug 1352233 will also fix reordering issues even if Android does that (as both the local and remote orders need to be considered).

Masayuki, we're sorry about this problem - we'll probably ask you to see if you can still reproduce a problem once those 2 bugs land.
Flags: needinfo?(markh)
See Also: → 1352947
Closing as a dupe of the meta which tracks work to fix this. Feel free to follow up with your experiences.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: