I can reproduce this issue on Windows 10
Signin-internals attached

Deleted: Untitled document.pdf 78.1 KB

Untitled document.pdf 78.1 KB Download

User feedback : https://feedback/product/237/neutron?lView=rl&lRSort=1&lROrder=2&lRFilter=1&lReportSearch=sign%20in%20details%20are%20out%20of%20date

Marking this as RB-Stable for now for tracking. I tried to replicate this but was unable to on Mac.

Unable to reproduce this issue on Ubuntu 14.04, Windows-10 and Mac OS 10.12.13 using chrome latest stable #62.0.3202.75 by following steps mentioned in the original comment. Observed the chrome stays signed in and no error message is displayed after re opening the chrome.

Note: Tested this issue on fresh install and also by upgrading from older version to latest stable version, still issue is not seen.

jainabhishek@ Is this issue is seen specific to any particular account or every account?

Thanks!

Getting this error on my google profile.
Every time I close chrome and re-open I have red exclamation next to profile name which says Sign-in details out of date.

I sign in again and it logs me out of all signed in webpages (mail, calendar, hangouts etc).

So I close chrome again, sign into Chrome profile, sign into Google apps and repeat the process again after I close Chrome or Windows force reboots :P

I have attached Signin-internals in this bug, happy to debug it further.

+ewald@ +zea@

jainabhishek@ - I tried repro steps in #6. However unable to recreate it. 

1) it appears that when jainabishek@ closes chrome , and re-opens red exclamation is shown indicating sign-in required to sync. Is that expected flow that sign-in required after browser is closed?

2) Signing-in into Chrome profile logs jainabhishek@ out of existing sign-in apps. Which sounds like shouldn't happen. 

Adding the sign-in engineering team. Mihai, I seem to recall there was another bug like this a while back, where Chrome was failing to read the profile data on startup for some reason.

Does this seem like another instance of that?

There were 2 issues that are similar:
*  Issue 744626  : This was a problem with an Windows API that was not storing data correctly on disk. I doubt this is related to the issue here as folks complain of this new problem on mac machines as well.
*  Issue 767129  : This was a problem with the account that was locked somehow on the server. Every time the user attempted to sign in, the sync server forced it to be signed out. This may be the cause for the current bug as well.

I think we would need from the users the following addition information:
* Open chrome://sign-internals and send us a screenshot. Note that this will contain user data like the email of the users.
* Open chrome://sync-internals and send us a screenshot.
* Open chrome://version and send us a screenshot.

I doubt that this is related to our experiment for DICE fixing auth errors as the forum entries started at the beginning of October, which is before M62 shipped.

First of all, I'm taking RBS off because I don't think there's a high likelihood of a major regression with sign-in/sync here. I'll keep it as P1 for visibility for now, but may bump down to P2 later.

jainabhishek - can you ask these users for screenshots of chrome://signin-internals, chrome://sync-internals, and chrome://version?

Friendly ping. We need more info from the reporters to be able to debug this issue.

Downgrading to P2 since we're not seeing more reports of this, so I doubt it's an urgent issue.

Can someone please follow-up with additional details from the reporters? If we can't get any additional information, we'll have to mark this as WontFix.

Friendly ping for jainabhishek@. We can't do any more debugging until we see more details of what's happening.

If we don't receive any feedback in the next few days, I'm going to close this out as WontFix.

Closing this out due to lack of feedback.