Top Sites from NTP are not synced between devices |
||||||||
Issue descriptionApp Version: 61.0.3163.20 beta iOS Version: 10.3.3, 10.2.1 Device: iPad, iPhone URL: na Steps to reproduce: 1. Take two iOS devices (both iPads or iPhones) 2. Fresh Install Google Chrome on device#1 3. Sign in with any testaccount that has most likely tiles displayed in NewTabPage 4. (IF NOT, then Sign in and visit atleast 8sites multiple times to create some data) 5. Now, make a fresh install on second device, Device#2 6. Launch Google Chrome and Sign in with the same testaccount previously used. 7. Wait for sync to complete. (Force quit and launch app few times as well) Observed results: TopSites data from the device#1 account is never displayed in the NewTabPage of the device#2. Device#2 is always showing the PopularSites even after waiting for longtime. All other data (History,Bookmark etc) are synced correctly on to device#2. Expected results: TopSites should be synced and NewTabPage should be updated correctly with the data specific to the testaccount Number of times you were able to reproduce: 5/5 Bug reproducible after clean install: Yes Bug reproducible after clearing cache and cookies: Yes Bug reproducible on Chrome Mobile on Android: NotTested Bug reproducible on Safari/Firefox: Firefox: NA, Safari: NA Bug reproducible on current stable build (App Version, iOS Version): M60 Yes Bug reproducible on the current beta channel build (App Version, iOS Version): M61 Yes
,
Jul 31 2017
Displaying most visited sites relies on the presence of segments data in HistoryDB (segment_usage table). We don't sync this data for newly created profiles.
,
Jul 31 2017
I didn't see them syncing atleast in a interval of 20mins. I can try again sometime later. But on device#2 if I start loading new websites, they displayed as TopSites on that device.
,
Aug 1 2017
+treib@: should top sites be synced?
,
Aug 1 2017
Well.. it's complicated. TopSites themselves are computed based on local history, and are not synced. However, if you have history sync enabled and have a sufficient amount of synced data in your account, then you should eventually receive MostLikely (based on *synced* history) instead of TopSites, so then all devices should be in sync. "sufficient amount of synced data": I don't remember the exact numbers, but it is something around at least 30 history entries from at least 8 different web sites. It can also take a while, up to an hour or so, until MostLikely gets updated. So, possible explanations: - The test account doesn't have enough synced history. - MostLikely was just slow. - Something is broken with MostLikely on iOS. UMA looks reasonable though, so I don't think so.
,
Aug 1 2017
Is it possible to test again following the steps in #5?
,
Aug 1 2017
May be MostLikely is Slow? I was using a regular test account which has definitely lots of History from lots of different websites, and noticed this issue with that account. So then to repro I started of with another testaccount clearing all browsing history and with just 8 different websites in History. I will try to test a little bit more and update.
,
Aug 1 2017
FYI, we are working on reducing the number of required distinct tiles such that these scenarios are less likely.
,
Aug 1 2017
I just tested this on same set of devices and with same account. And MostLikely sites are displayed immediately. There is no delay at all. For some reason yesterday it is not syncing even after 15-20mins. Please let me know If I can close this bug.
,
Aug 1 2017
Yes, I think with this info it can be closed. MostLikely *typically* updates within a minute or so, but sometimes takes a lot longer. As long as it doesn't take more than an hour or so, this is okay.
,
Aug 1 2017
Yes, it looks ok. I think we can close it.
,
Aug 1 2017
Thanks for checking and detailed clarifications. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by pkl@chromium.org
, Jul 31 2017Labels: M-61
Owner: gambard@chromium.org
Status: Assigned (was: Untriaged)