Issue metadata
Sign in to add a comment
|
Everytime I close and reopen my Chrome content isn't syncing. Most notably my passwords or auto signons aren't working.
Reported by
jb.popla...@gmail.com,
Feb 8 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce the problem: 1. Close Chrome 2. Reopen Chrome 3. Notice top right Username has a red sync error What is the expected behavior? I open chrome and it auto signs in and/or doesn't have a broken sync issue top right. What went wrong? Not signing in as expected. Did this work before? Yes Last one? Not sure, my Chrome is up to date as possible. Chrome version: 56.0.2924.87 Channel: stable OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 24.0 r0 Another user at the office is also broken. At first we thought the Cyber team was blocking something. But I'm at home and still have problems.
,
Feb 8 2017
Can you take screen shots and attach chrome://sync-internals and chrome://signin-internals to this bug?
,
Feb 8 2017
,
Feb 9 2017
Sorry for the delay. Attached the output as requested. I did get the latest Chrome pushed to me on Saturday through corporate policy. Just wondering if something is conflicting on my box. I'm a local admin on the box.
,
Feb 9 2017
It looks like your sign in data is no longer being accepted. There are various reasons this could happen. But it should be very infrequent. If you go to settings and you re-sign in, does this fix things? If so, do they break again shortly after?
,
Feb 9 2017
Tried a few times. Appears to take but once I sign out and in it's back to broken. Was concerned I'm under a policy that's blocking cookies from being saved or something. No policy change just the new update. Update works fine on my home PC (windows, no work policy). Wondering if a policy was dormant and now in effect. Anything else to try or just wait for next release? I attempted to uninstall but couldn't. Could bring back to Desktop support and see what they say. I can get my passwords from passwords.google just a pain to have to enter my passwords again for gmail, FB and slack.
,
Feb 9 2017
Adding sign in to this bug. When you said > Appears to take but once I sign out and in it's back to broken. I'm confused. Are we just talking about re-signing into Chrome? Or are you talking about signing out of your OS? Even if logging out and back into your OS breaks things, it should have had time before that to properly sync all of your data down, and things like passwords should be in your local passwords storage. There has to be something blocking that initial signin from working, somehow. Can you re-sign into Chrome again, and then grab chrome://sync-internals and chrome://signin-internals again?
,
Feb 10 2017
Just to add to what skym@ is saying, there should be a blue button underneath the error you took a screenshot of that says "Sign in again." Clicking that button should bring up a modal dialogue with a blue header to allow you to re-authenticate. See attached screenshots. After going through that re-authentication flow, your profile should start syncing again, and all of your passwords, autofill data, etc. should be synced down, so that the next time you go to gmail, FB, slack, etc. it should be autofilled for you. Can you please confirm that you're going through the re-authentication flow I described above? Please take a screenshot of chrome://signin-internals and chrome://sync-internals after you do that. Are you saying after doing that, when you sign out and back into your OS user, you get the same error message again?
,
Feb 11 2017
Thanks. Here's what I've found. When I click the sign in button, I'll stay signed in until I close Chrome (Command + Q). Reopen and it doesn't remember my sign in. More or less, every time I close Chrome, I lose every sign in I had. IE, if I sign into Slack. Close Chrome and reopen, I have to resign back into Slack. Going to try resetting my chrome settings, unless there's any other suggestions.
,
Feb 13 2017
It sounds like Chrome is having trouble writing to persistent storage, wherever that is. If you open chrome://version/ you can see the "Profile Path", but I think for OSX we store credentials slightly differently. +vasilii who's more familiar with sign in on OSX.
,
Feb 13 2017
Deleted the profile1 folder and relaunched and signed in. I'm back in business! Closed and opened a few times and it's working like a charm. Thanks everyone!
,
Feb 14 2017
Closing then! Glad to hear things are working. Feel free to reopen if this occurs again. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ajha@chromium.org
, Feb 8 2017