Closed Bug 982273 Opened 11 years ago Closed 11 years ago

[Nightly 2014-03-11] Sync (1.1) bookmark from Android fails on Desktop Nightly but works on Desktop Release

Categories

(Firefox :: Sync, defect)

Product:
Firefox
Component:
Sync
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: kthiessen, Unassigned)

Details

[Fennec Release (27.0) on Android (Nexus 7) and Nightly 2014-03-11 on Desktop (Mac OS 10.8)] Please note: This is Legacy Sync (1.1), not FxA Sync. STR: 1. Bookmark http://nightly.mozilla.org on Android. 2. Cause Android to Sync via the menu. 3. Start Nightly on Desktop with a Legacy Sync Profile, pull down 'Sync Now' from the menu, wait 2 minutes. result: no bookmark expected: bookmark shows up under 'mobile bookmarks' 4. Start Release 27.0 Firefox on Desktop with same profile, pull down 'Sync Now' from menu, wait 2 minutes. result: there's the bookmark. Am I doing something terribly wrong here?
What happens if you (after backing up places.sqlite) choose "Reset Sync > Replace contents of this device" from Sync Preferences on the desktop?
Component: Sync → Firefox Sync: Backend
Product: Firefox → Mozilla Services
Version: 29 Branch → unspecified
All my bookmarks get shiny new timestamps, my add-ons get re-installed, and ... the bookmark shows up.(In reply to Richard Newman [:rnewman] from comment #1) > What happens if you (after backing up places.sqlite) choose "Reset Sync > > Replace contents of this device" from Sync Preferences on the desktop? All my bookmarks get shiny new timestamps, my add-ons get re-installed, and ... the bookmark is still there, with the shiny new timestamp. So apparently it was in the Sync data.
If two devices are racing -- that is, one of them is uploading while the other is downloading -- the downloading client will never see the uploaded record. This is an unfortunate reality of the Sync protocol: it was never designed for frequent, multi-client use.
Yeah. this is looking like a combination of User Impatience and the above-mentioned race condition. Thanks for the amazingly quick response. Closing as INVALID.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
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.