Some URLs are not syncing properly with all the devices in sync chain #25650
Labels
bug
closed/invalid
feature/sync
OS/Android
Fixes related to Android browser functionality
OS/Desktop
OS/iOS
Fixes related to iOS browser functionality
QA/Yes
Description
Not all the TYPED History is being synced between every device in sync chain.
The TYPED history is working with intermittent problems and which url syncs when is not consistent at all. It almost feels like there is window like period it syncs and it stops after.
More than one occasion we witnessed a typed url from a device might appear in one device but not in another. And in addition when a typed url is sent from a device, there is an increase in number
Typed Urls
sometimes this url being synced from other device is not shown insideSync Node Browser
and does not appear in History at all.Steps to Reproduce
Actual result:
Not every url is synced, sometimes url is not synced with any device, sometimes it synced partially with some of the devices.
For instance
brave.com
is typed on Android device and it is received on iOS device however it is not synced on Desktop.Or
reddit.com
is typed on desktop, received by android but not iOS orreddit.com/r/news
is typed on iOS which is received by Android but not on desktop. And some urls typed are not received by either of devices.Also on similar note as mentioned above what is observed on desktop side inside
Sync Internals
is sometimes when a typed url is entered from a device, the increase in numberTyped Urls
can be observed but this url being synced from other device is not shown insideSync Node Browser
and does not appear in History at all.Expected result:
The typed urls should sync across all the devices properly.
Reproduces how often:
The issue is 100 percent reproducible as long as more urls are being typed eventually this will be observed. Which means it is not depending on what urls is typed on which device.
Desktop Brave version:
Latest Nightly on MacOS / Windows
Android Device details:
Version/Channel Information:
N/A
Other Additional Information:
Miscellaneous Information:
The behaviour is tested on Chrome and it is working as expected. cc @Brandon-T @AlexeyBarabash
The text was updated successfully, but these errors were encountered: