Does not allow me to stay logged in to chrome
Reported by
jtgo...@gmail.com,
Aug 3
|
|||||||||
Issue descriptionENVIRONMENT and STATS For syncing clients: From chrome://version, Google Chrome 68.0.3440.84 (Official Build) (64-bit) Revision 520a5c14b858e4b1441dd2d3bab9bc745911a23b-refs/branch-heads/3440@{#774} OS Mac OS X From about:sync, copy/paste the tab contents here, or select the Data tab and click [Dump sync events to text]. ====== Status ====== { "actionable_error": [ { "is_valid": false, "stat_name": "Error Type", "stat_value": "Uninitialized" }, { "is_valid": false, "stat_name": "Action", "stat_value": "Uninitialized" }, { "is_valid": false, "stat_name": "URL", "stat_value": "Uninitialized" }, { "is_valid": false, "stat_name": "Error Description", "stat_value": "Uninitialized" } ], "actionable_error_detected": false, "details": [ { "data": [ { "is_valid": false, "stat_name": "Summary", "stat_value": "Uninitialized" } ], "is_sensitive": false, "title": "Summary" }, { "data": [ { "is_valid": true, "stat_name": "Client Version", "stat_value": "Google Chrome Mac OS X 68.0.3440.84 (520a5c14b858e4b1441dd2d3bab9bc745911a23b-refs/branch-heads/3440@{#774}) stable" }, { "is_valid": true, "stat_name": "Server URL", "stat_value": "https://clients4.google.com/chrome-sync" } ], "is_sensitive": false, "title": "Version Info" }, { "data": [ { "is_valid": false, "stat_name": "Sync Client ID", "stat_value": "Uninitialized" }, { "is_valid": false, "stat_name": "Invalidator Client ID", "stat_value": "Uninitialized" }, { "is_valid": true, "stat_name": "Username", "stat_value": "" } ], "is_sensitive": true, "title": "Identity" }, { "data": [ { "is_valid": true, "stat_name": "Requested Token", "stat_value": "n/a" }, { "is_valid": true, "stat_name": "Received Token", "stat_value": "n/a" }, { "is_valid": true, "stat_name": "Token Request Status", "stat_value": "OK" }, { "is_valid": true, "stat_name": "Next Token Request", "stat_value": "not scheduled" } ], "is_sensitive": false, "title": "Credentials" }, { "data": [ { "is_valid": true, "stat_name": "Server Connection", "stat_value": "not attempted" }, { "is_valid": true, "stat_name": "Last Synced", "stat_value": "Never" }, { "is_valid": true, "stat_name": "Sync First-Time Setup Complete", "stat_value": false }, { "is_valid": true, "stat_name": "Sync Engine State", "stat_value": "Not started" }, { "is_valid": false, "stat_name": "Sync Cycle Ongoing", "stat_value": false }, { "is_valid": true, "stat_name": "Local Sync Backend Enabled", "stat_value": false }, { "is_valid": false, "stat_name": "Local Backend Path", "stat_value": "Uninitialized" } ], "is_sensitive": false, "title": "Local State" }, { "data": [ { "is_valid": false, "stat_name": "Throttled or Backoff", "stat_value": false }, { "is_valid": false, "stat_name": "Retry Time", "stat_value": "Uninitialized" }, { "is_valid": false, "stat_name": "Notifications Enabled", "stat_value": false } ], "is_sensitive": false, "title": "Network" }, { "data": [ { "is_valid": false, "stat_name": "Explicit Passphrase", "stat_value": false }, { "is_valid": false, "stat_name": "Passphrase Required", "stat_value": false }, { "is_valid": false, "stat_name": "Cryptographer Ready", "stat_value": false }, { "is_valid": false, "stat_name": "Cryptographer Has Pending Keys", "stat_value": false }, { "is_valid": false, "stat_name": "Encrypted Types", "stat_value": "Uninitialized" }, { "is_valid": false, "stat_name": "Has Keystore Key", "stat_value": false }, { "is_valid": false, "stat_name": "Keystore Migration Time", "stat_value": "Uninitialized" }, { "is_valid": false, "stat_name": "Passphrase Type", "stat_value": "Uninitialized" }, { "is_valid": false, "stat_name": "Passphrase Time", "stat_value": "Uninitialized" } ], "is_sensitive": false, "title": "Encryption" }, { "data": [ { "is_valid": false, "stat_name": "Sync Source", "stat_value": "Uninitialized" }, { "is_valid": false, "stat_name": "GetKey Step Result", "stat_value": "Uninitialized" }, { "is_valid": false, "stat_name": "Download Step Result", "stat_value": "Uninitialized" }, { "is_valid": false, "stat_name": "Commit Step Result", "stat_value": "Uninitialized" } ], "is_sensitive": false, "title": "Status from Last Completed Session" }, { "data": [ { "is_valid": false, "stat_name": "Notifications Received", "stat_value": 0 }, { "is_valid": false, "stat_name": "Updates Downloaded", "stat_value": 0 }, { "is_valid": false, "stat_name": "Tombstone Updates", "stat_value": 0 }, { "is_valid": false, "stat_name": "Reflected Updates", "stat_value": 0 }, { "is_valid": false, "stat_name": "Successful Commits", "stat_value": 0 }, { "is_valid": false, "stat_name": "Conflicts Resolved: Client Wins", "stat_value": 0 }, { "is_valid": false, "stat_name": "Conflicts Resolved: Server Wins", "stat_value": 0 } ], "is_sensitive": false, "title": "Running Totals" }, { "data": [ { "is_valid": false, "stat_name": "Encryption Conflicts", "stat_value": 0 }, { "is_valid": false, "stat_name": "Hierarchy Conflicts", "stat_value": 0 }, { "is_valid": false, "stat_name": "Server Conflicts", "stat_value": 0 }, { "is_valid": false, "stat_name": "Committed Items", "stat_value": 0 } ], "is_sensitive": false, "title": "Transient Counters (this cycle)" }, { "data": [ { "is_valid": false, "stat_name": "Updates Downloaded", "stat_value": 0 }, { "is_valid": false, "stat_name": "Committed Count", "stat_value": 0 }, { "is_valid": false, "stat_name": "Entries", "stat_value": 0 } ], "is_sensitive": false, "title": "Transient Counters (last cycle of last completed session)" }, { "data": [ { "is_valid": false, "stat_name": "Server Invalidations", "stat_value": 0 }, { "is_valid": false, "stat_name": "Local Changes", "stat_value": 0 }, { "is_valid": false, "stat_name": "Local Refreshes", "stat_value": 0 } ], "is_sensitive": false, "title": "Nudge Source Counters" } ], "type_status": [], "unrecoverable_error_detected": false } ============= Notifications ============= undefined === Log === [] REPRO STEPS 1. click top right link on chrome where it has my name, currently reads "Taylor - Home" 2. select sign-in to chrome 3. input username 4. input password 5. screen animation shows that i logged in 6. drop down option states "you've singed in and turned on Sync" 7. click "ok-got it" ACTUAL RESULTS After the above nothing changes. Chrome does not sync anything (e.g. history, bookmarks, extensions, etc.). When I navigate to google.com it shows my image in the top right of the webpage indicating that i have logged in, but nothing has synced. It also includes my name on the top right of the browser. But when i click my name, it tells me again that I need to log in. This is browser independent. When i try to log in at work on a Windows 10 PC running the latest public build of chrome i get the exact same results. When i log in with an alternate username, everything syncs normally. In other words it feels more like it is dependent on my username rather than the browser. EXPECTED RESULTS Chrome to sync. (i.e. history, bookmarks, extensions, etc.) ADDITIONAL INFO Anything else which may help us debug the issue; screenshots of error messages or states are always helpful.
,
Aug 8
Mihai, another sign-in issue.
,
Aug 8
Adding sync folks as this may be a sync configuration for the account. 1. Chrome sign-in flow happens as Chrome gets a valid token, we present the sync confirmation dialog. 2. What I suspect is that there is an even that triggers a sign-out. This event is most probably related to the account that triggers a log out. It may be reflated to somehow sync being disabled server-side for this account. Mac/Mikel: Would you know how the user could check whether sync is disabled for this account?
,
Aug 8
The only situation where Sync will sign you out is if you do "Reset Sync" on https://chrome.google.com/sync. It doesn't look like that's the case here; that should only happen if you're already signed in at the time of the reset, and of course only once per device. Also, if there were any error coming from Sync, that should show up as either an actionable_error or unrecoverable_error, and neither is the case here. So, I agree that *something* seems to trigger a sign-out, but I don't think it's Sync.
,
Aug 23
--Chrome Identity automated triaging-- This bug is Untriaged and has gone for two weeks without any activity, so it is being moved to Available. Please see https://goo.gl/78kbny for more details. Please remove the Services>SignIn or UI>Browser>Profiles components if this bug isn't related to Chrome Identity. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 23
jtgooch@ - are you still able to reproduce this?
,
Aug 24
Unfortunately, it still is. I have tried this on multiple computers, and end up with the same result each time. Let me know if there is any information i could give you to help in this process. Taylor
,
Aug 24
Assigning to David to take a look. Taylor, could you please attach a screenshot of chrome://signin-internals from just after you try signing in (and get signed back out)? David - is there any other information we could use to help debug?
,
Sep 4
Sorry for the delay all, I have been on vacation. I very much appreciate you all still looking into this. There has now been a change though. Chrome has updated in my absence. I am now running Version 68.0.3440.106 (Official Build) (64-bit) on my Mac. Chrome is now letting my jtgooch user stay logged in, but it is not syncing between devices. I specifically added an extension and changed the theme on my chrome on my Mac to see if changes would sync between it an chrome on my PC, and it did not sync. I have tested other usernames on my computers, and those still work. Let me know if you need more info. Taylor
,
Sep 6
Please try updating Chrome to the latest version (version 69, by visiting chrome://chrome), restarting Chrome, and seeing if that fixes your issue. If it doesn't, please attach a screenshot of chrome://sync-internals.
,
Sep 17
I still get the issue (wont sync between browsers/computers), except that now it will keep my logged in but won't sync my info. When i go into settings and tell it to keep my stuff synced between browsers it will not remember my selection. See that attached video for how it is now presenting.
,
Sep 17
And here is a screen shot of chrome://sync-intervals. Thank you for continuing to help me with this problem.
,
Sep 17
On the screenshot of comment #9, I see that there is a Sync token, but no cookie. Could you check that cookies are not blocked? chrome://settings/content/cookies?search=cookies What is the value of: * "Allow sites to save and read cookie data" * "Block third-party cookies" This would explain why the cookies are missing. Maybe it could also cause Sync to fail, but that I'm not sure. The video on comment #11 looks like a sync issue, because the sync confirmation screen is shown, which means that the authentication succeeded, but somehow Sync does not start.
,
Sep 17
Interesting thing on the screenshot in #9: There's an Actionable Error, with Error Type NOT_MY_BIRTHDAY and Action DISABLE_SYNC_ON_CLIENT. I think that's exactly what happens after you reset Sync via the dashboard, but of course, turning Sync on again should resolve it. I guess if the Sync server keeps sending that error for some reason, we'd expect this behavior in Chrome?
,
Sep 17
I think the problem may be related to: https://cs.chromium.org/chromium/src/components/sync/driver/sync_service.h?rcl=6f5924df224f88c7618a4cd98849de08b5a25570&l=79 As indicated by the sync-internal screenshot above.
,
Sep 17
I don't think so. After a "Reset Sync" from the dashboard, that reason is expected, and turning Sync on again should make it go away.
,
Sep 17
treib: The "summary" field says: "Not signed in, User choice". Apparently signing again does not resolve the problem, what do you think could be the cause?
,
Sep 17
What I think happens is that signing in again *does* resolve those, but then the Sync server immediately sends the error with NOT_MY_BIRTHDAY and DISABLE_SYNC_ON_CLIENT again, which causes Chrome to sign you out again. So the question would be, why does the server keep sending this error?
,
Sep 17
So does this seem more likely to be a sync server issue than a sign in issue? Should we re-assign to someone on the sync server team?
,
Sep 18
+sfiera for the server: Any ideas why the server might repeatedly send an error with NOT_MY_BIRTHDAY / DISABLE_SYNC_ON_CLIENT? (Or any way to figure out if that's actually happening?)
,
Sep 18
It’s difficult to say without knowing what the birthdays in question are. Without more information, my best hypothesis is that the server has some corrupted data with a birthday in the future. Trying to sync it down would result in NOT_MY_BIRTHDAY, but I don’t think the server would ever clean it up (even after resetting Sync from the dashboard, unfortunately). It would be useful to know if the Sync account has a passphrase (https://support.google.com/chrome/answer/165139), since the birthday and passphrase flows are somewhat related.
,
Sep 23
Is there another way to tell if the Sync account is encrypted? As you can see from the above video, it won't actually let me into the setting to see if it is encrypting the sync data. I do remember that years and years ago i did have sync encrypted, but I am not now prompted for that password and I think I turned it off.
,
Sep 23
So I went to reset my sync password, and discovered something interesting, it says that my account is empty.
,
Sep 24
Resetting your Sync password will clear all your Sync data from our servers, so it's expected that your account is empty afterwards. If you now enable Sync again in Chrome, it should re-upload all your data. For future reference, you could have told that your Sync data is encrypted by the "lock" icons next to all types on https://chrome.google.com/sync.
,
Sep 24
My understanding is that the account was already reported as having no data--which I think makes sense if some corrupt data marked as being “from the future” prevents Sync from working. I’ll run an analysis in the next few days to see if we have any data that’s corrupt in this way.
,
Sep 24
Correct. It did not let me reset sync. Instead, it provided the error message saying that my sync data was empty. Thanks again everyone for helping and @sfiera, I look forward to learning what you find out.
,
Oct 2
Sorry, but I didn’t get a chance to test this last week, and will not this week either.
,
Oct 2
Thanks for the update. Taylor
,
Oct 17
Hey sfiera, any chance you got a chance to run the test?
,
Oct 25
Finally got this all the way done. It turns out that yes, there are a small number of users in this state, but you’re not one of them. So, that theory’s bust. I still think that there must be some bad data in your account. In order to determine what is wrong, we’d need to look at your data and logs stored with Google. We can’t do that without your consent, so if you’re willing to let us do that, reply here saying so. Otherwise, we’ll keep your issue in mind, but I don’t know what else we can do.
,
Oct 25
Assuming that this would not extend to my gmail or gchat history, i am fine with you accessing my data and logs stored with Google.
,
Oct 26
Yes, I can’t look at anything on pages you visit. It turns out your account is in a similar but slightly different state. At some point in the past, you appear to have reset your Sync account through chrome.google.com/sync and cleared out the data. You started using Sync again with new data. For some reason, our system records the birthday of the new account as being earlier than the old account. We’ll discuss how best to safely clear out the corrupt data and get back to you.
,
Oct 26
Interesting. Thanks for the update.
,
Nov 6
SFiera, I was wondering if you were ever able to determine a safe way to clear the corrupt data out? Taylor
,
Nov 7
We determined a way that we think should work, but haven’t yet been able to complete the process. Still working on it.
,
Nov 13
I’ve (virtually) hit the reset button for you. If all works as predicted, you should now be able to log into Sync and start using it.
,
Nov 14
IT WORKS!!! Thank you for fixing it. I know that it took you a little while and I really appreciate you taking the time to solve this problem. It had been driving me nuts for a couple years. Thank you. Taylor
,
Nov 14
Great, thanks for helping us find our bug! |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by jtgo...@gmail.com
, Aug 310.3 MB
10.3 MB View Download