722724 - History is synced randomly

Status: RESOLVED INCOMPLETE

(Firefox for Android Graveyard :: Android Sync, defect, P2)

Description

[Andreea Pod]

Attachment: device

Mozilla /5.0 (Android;Linux armv7l;rv:11.0a2) Gecko/20120131 Firefox/11.0a2 Fennec/11.0a2
Device: LG optimus 2X (Android 2.2)

Steps to reproduce:
1. set up sync on desktop and a device
2. make some history 
3. refresh sync on both (device and desktop)

Expected results:
- the entries in the history list should look the same for both

Actual result:
- pages are synced randomly(see screenshots)

Comment 1

[Andreea Pod]

Attachment: desktop

Comment 2

[Richard Newman [:rnewman]]

Can you provide a log (as described here: http://160.twinql.com/how-to-file-a-good-android-sync-bug) and steps to reproduce?

How are you triggering a sync on the Android device?

Comment 3

[Andreea Pod]

Attachment: LG log

So, today I tried to reproduce this again so I could take the log. I followed next steps:
- cleared the profile on Android and on Desktop
- set up sync on Desktop and set the option to "Replace all other devices with this computer's data" so the sync account data is replaced with the new data.
- paired a device(LG Optimus 2X - Android 2.2.2)
- visited some sites on desktop and device and then refresh sync 2 times so to make sure that all the date was transferred. 

=> all worked fine, history list had the same entries on both desktop and device.

- paired another device (Motorola Droid 2 - Android 2.3.3) using "Pair a device" from desktop.
- synced both devices and desktop more than once

=> history on devices is not the same like on desktop, at a moment it was all erased on device.

I attached the log from LG and a sync log from computer from about:sync-log. If you need more info pleas let me know.

Comment 4

[Andreea Pod]

Attachment: sync log desktop

Comment 5

[Tracy Walker [:tracy]]

rnewman, is it possible the change talked about https://bugzilla.mozilla.org/show_bug.cgi?id=721898#c7 is causing this?  if mobile devices are pruning so markedly,  I imagine users will begin to immediately notice odd disparity in history collections on each device.

UX when creating a stump of History tree really sucks.  what's the point of syncing to a mobile device if it's only going to carry 300 history items. :-(

Comment 6

[Richard Newman [:rnewman]]

(In reply to Tracy Walker [:tracy] from comment #5)
> rnewman, is it possible the change talked about
> https://bugzilla.mozilla.org/show_bug.cgi?id=721898#c7 is causing this?

That was my first guess, but it doesn't sound like there were more than 300 visits on the device, and the log certainly isn't big enough to suggest that.

There are a lot of items apparently with 0 visits. That might be a logging artifact, though.

Gonna set this as a P1, because something ain't right.

Comment 7

[Allison Naaktgeboren :ally]

agree with the p1 ranking.

Comment 8

[Richard Newman [:rnewman]]

… then I'll put it back :D

Comment 9

[Richard Newman [:rnewman]]

I'm pretty sure this is caused by timestamp handling. Will verify after that's implemented.

Comment 10

[Richard Newman [:rnewman]]

Let's see if this still happens.

Comment 11

[Adrian Tamas (:AdrianT)]

I am unable to reproduce the issue on Nightly/14.0a1 2012-04-12 in several tries. I have created a clean sync profile on Desktop (Linux x86 using the latest Firefox release).
I have synced 2 devices HTC Desire (Android 2.2) and Motorola Droid 2 (Android 2.3) and have done different syncs - from desktop to the devices, from the devices to the desktop, between the devices. All History items are synced in the correct order. I am seeing that on the devices pages that do the redirects - like when logging into yahoo mail or at cnn.com are not synced - but the synced history entries are in order.

Comment 12

[Ioana Chiorean]

Should it be closed as WFM?

Comment 13

[Richard Newman [:rnewman]]

(In reply to Ioana Chiorean from comment #12)
> Should it be closed as WFM?

I opted for INCOMPLETE, because WFM implies that I managed to reproduce the exact scenario but didn't have a problem. INCOMPLETE suggests that there's no obvious next step to take.

I don't mind at all if you want to change that; it's the RESOLVED part that matters to me :)