Issue metadata
Sign in to add a comment
|
Bookmarks are not syncing (SYNC AUTH ERROR) |
||||||||||||||||||||||
Issue descriptionI first noticed this problem sometime last week. We are also getting external feedback that sounds similar. Chrome 68.0.3431.0 dev Repro steps: 1) Open bookmarks on iPhone and navigate to a folder with bookmarks. 2) Open that same folder in the desktop bookmarks manager. 3) Make a change in that folder. Add a new bookmark. Delete a bookmark. Reorder two bookmarks. On my Android phone, I see the updates show up after about 10 seconds. On the iPhone, my bookmarks never change. Things that do not work to get bookmarks synced: - Closing and reopening bookmarks. - Going up a folder and then back down again. - Reloading chrome://sync-internals - Pressing the "Trigger GetUpdates" button. Things that do work: - Quitting and relaunching Chrome. I've attached a partial screenshot of sync-internals (can send the whole thing upon request). It looks like the initial sync works, and then I get a SYNC AUTH ERROR that might be preventing further syncs?
,
May 16 2018
Thanks for duping! I had a couple questions: 1) Issue 843139 sort of implies that this only hit new installs, but I've had this app installed for at least six months. Can that issue affect old installs as well? 2) I noticed this last week as well -- would that timeframe still be covered by Issue 843139?
,
May 16 2018
As documented elsewhere, the steps to verify if you're affected by the issue are: Visit chrome://invalidations -- if the service state is TRANSIENT_INVALIDATION_ERROR, your Chrome instance is affected We know that most recent versions of Chrome (so very likely on dev) cause this issue for old clients as well after 1 week, so you may fall in that category. I believe that you'd still see the TRANSIENT_INVALIDATION_ERROR described above. We do expect that a fix will go live very soon.
,
May 16 2018
There's been another roll-out which also triggered this for existing clients. This is rolled back. Can you restart your browser (potentially twice) and see if the problem still persists? a screenshot of chrome://invalidations will help to diagnose the problem and verify it's gone.
,
May 16 2018
This is dev channel so the recent Finch changes are irrelevant. On dev, there is an ongoing 50% experiment.
,
May 16 2018
chrome://invalidations doesn't work on iOS. Would that be useful to bring up? |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by mastiz@chromium.org
, May 16 2018Mergedinto: 843139
Status: Duplicate (was: Untriaged)