-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bookmarks on device where sync was reset isn't sent across the chain #3188
Labels
bug
feature/sync
priority/P2
A bad problem. We might uplift this to the next planned release.
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Yes
release-notes/exclude
Milestone
Comments
rebron
added
priority/P3
The next thing for us to work on. It'll ride the trains.
priority/P2
A bad problem. We might uplift this to the next planned release.
and removed
priority/P3
The next thing for us to work on. It'll ride the trains.
labels
Feb 1, 2019
18 tasks
This was referenced Feb 7, 2019
Verification passed on
Used STR from brave/brave-core#1560. Verification passed on
Verified passed with
|
This was referenced Mar 1, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
feature/sync
priority/P2
A bad problem. We might uplift this to the next planned release.
QA Pass-Linux
QA Pass-macOS
QA Pass-Win64
QA/Yes
release-notes/exclude
Description
Bookmarks on device where sync was reset isn't sent across the chain.
Devices
Device 1: Samsung Tab running 1.0.76
Device 2: Pixel 3XL running 1.0.76
Device 3: Linux running 0.59.34 profile 1 (Sync already created and reset)
Device 4: Linux running 0.59.34 profile 2
Steps to Reproduce
Actual result:
Device 1
Device 2
Device 3 (Contains 2 bookmark folder
Linux
andWindows
which doesn't sync)Device 4
Expected result:
Irrespective of previous sync state all bookmarks should be sync'd across all devices
Reproduces how often:
Easy
Brave version (brave://version info)
Android Build 1.0.76
Reproducible on current release:
Website problems only:
Additional Information
cc: @SergeyZhukovsky @brave/legacy_qa @AlexeyBarabash @darkdh
The text was updated successfully, but these errors were encountered: