Skip to content
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

Sync client gets into loop with RECONFIGURATION or NEWLY_SUPPORTED_DATATYPE #38101

Open
urbenlegend opened this issue May 6, 2024 · 5 comments
Labels

Comments

@urbenlegend
Copy link

Description

I tried adding a new device to my sync chain. It managed to sync my bookmarks, but when I enable the option to "Sync everything", it now no longer works properly. My extensions are never synced and brave://sync-internals is spamming a bunch of RECONFIGURATION messages:
image

The sync chain is also relatively new (2 weeks old). It isn't some old sync chain from back in the day that had sync issues.

Steps to Reproduce

  1. Add a new device to an existing sync chain
  2. Go into sync settings and enable "Sync everything"
  3. Notice that nothing else is properly synced and that brave://sync-internals is spamming the same RECONFIGURATION messages over and over again

Actual result:

Nothing except bookmarks can be synced. Enabling "Sync everything" makes sync go into an infinite loop of RECONFIGURATION messages

Expected result:

Everything is properly synced.

Reproduces how often:

Easily reproduced

Brave version (brave://version info)

1.65.126 Chromium: 124.0.6367.118 (Official Build) (64-bit)

Version/Channel Information:

  • Can you reproduce this issue with the current release? Yes
  • Can you reproduce this issue with the beta channel? Not tested
  • Can you reproduce this issue with the nightly channel? Not tested

Other Additional Information:

  • Does the issue resolve itself when disabling Brave Shields? No
  • Does the issue resolve itself when disabling Brave Rewards? No
  • Is the issue reproducible on the latest version of Chrome? N/A

Miscellaneous Information:

@urbenlegend
Copy link
Author

urbenlegend commented May 7, 2024

Turning off history sync and then restarting the entire browser seems to stop the infinite loop and allow syncing of the other categories. Re-enabling it again immediately causes the issue.

Seems like something borked with history sync.

My existing devices that were paired before are able to sync history though. It is only with newly paired devices that this issue occurs.

@urbenlegend
Copy link
Author

I ended up deleting the entire sync chain and just recreating a brand new one. Not sure what was borked with the previous one but this should be fixed to prevent confusion for other users.

@rebron
Copy link
Collaborator

rebron commented May 10, 2024

cc: @AlexeyBarabash

@AlexeyBarabash
Copy link
Contributor

@urbenlegend thank you for report

we are working on the sync server fix , the best for now to disable history sync, till we not deploy the fix.

@bsclifton
Copy link
Member

bsclifton commented May 14, 2024

I ran into this one myself - @AlexeyBarabash tried to reproduce, but wasn't able to.

Here are the steps I did:

  1. Got myself into a broken state (basically same symptoms as Sync chain randomly ceases working #35042)
  2. Turned off history sync
  3. Continued to use the product for a while (2 hours?)
  4. Turn back ON history sync
  5. Waited ~10 minutes - new sync happened (saw it happen on brave://sync-internals)
  6. Went to brave://sync-internals and saw traffic logs exploding with RECONFIGURATION
  7. Closed browser, waited a few mins
  8. Opened browser
  9. Went to brave://sync-internals and saw traffic logs exploding with NEWLY_SUPPORTED_DATATYPE

Here is some screenshots from when I hit the first error. You can see how fast it's going.
sync

And here's a static screenshot of the second one. It was spamming the server with transactions too- I just didn't get an animated pic.
image

@bsclifton bsclifton changed the title Unable to properly sync a newly added device Sync client gets into loop with RECONFIGURATION or NEWLY_SUPPORTED_DATATYPE May 14, 2024
@bsclifton bsclifton added bug needs-investigation A bug not 100% confirmed/fixed labels May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants