Tested the issue on Mac os 10.12.5/6 and windows 10 & 7 using chrome latest stable m60 #60.0.3112.90 and canary M62 #62.0.3178.0 and issue is not reproduced.

Attached screencast for reference.

@riclozcac.biz-- Could you please update your chrome to latest stable and try in a fresh chrome profile without any extensions and flas enabled and update us with your observations and help us by providing the screencast of the issue for better traiging.

Thanks!

Deleted: 752816.mp4 1.9 MB

	752816.mp4 1.9 MB View Download

Can you also attach screenshots of chrome://sync-internals and chrome://signin-internals

Here are the screen shots

Deleted: 1.PNG 136 KB

	1.PNG 136 KB View Download

Deleted: 2.PNG 57.9 KB

	2.PNG 57.9 KB View Download

Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Hmm, that all looks healthy. Was this taken right after you signed in? Can you take screenshots of chrome://sync-internals and chrome://signin-internals when it prompts you for to signin, but before you actually re-sign in?

Also, what UI surface exactly is asking you to sign into Chrome?

i guess you're right those were taken right after I signed in. I've uploaded new ones before I re-sign in. It asks me to sign-in every time I launch the chrome itself.

Deleted: a.PNG 44.0 KB

	a.PNG 44.0 KB View Download

Deleted: b.png 61.3 KB

	b.png 61.3 KB View Download

Deleted: c.PNG 83.4 KB

	c.PNG 83.4 KB View Download

Deleted: d.PNG 46.2 KB

	d.PNG 46.2 KB View Download

Thank you for providing more feedback. Adding requester "skym@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I'm not sure what would cause Chrome to suddenly lose access tokens but still think it was signed in. +msarda, can you or someone from signin take a look?

Thanks for your help guys. BTW, I don't know if it makes a difference, but I just wanna let you know that it only happens on my desktop. I'm using chrome on my phone and the login works perfect. 

Watching the video in #12, I'm surprising that the sync settings confirmations dialog isn't presented. Is this like a special re-auth scenario or is the signin flow being broken for some reason?

I'm not really sure, but that's what happens every time I launch my chrome. I think it asks me to re-authorize the login by re-signing-in. Then, when I am logging into different sites (i.e. yahoo mail, facebook, etc.), I am constantly being asked if I want to save my passwords, which I constantly do. But after relaunching the chrome, it goes back to the same issue.

Is this a known bug?

I think there is a problem on your Windows machine. It looks like Chrome fails to persist (or read) the authorization tokens. 

We had a similar problem in  Issue 744626  (see the solution at https://bugs.chromium.org/p/chromium/issues/detail?id=744626#c29 )

@riclozcac.biz-- Could you please check the comment #16 and update us if you are still able to reproduce the issue in latest stable #60.0.3112.101 , after trying out the solution from comment #16.

Thanks!

Hi there. To be honest, the procedures are quite confusing and I don't know how to go about it. Would you mind telling me the steps to take?

Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

--Chrome Identity automated triaging--

This bug is Unconfirmed and has gone two weeks without any activity, so it is being closed as WontFix. Please re-open if this is still a valid and reproducible bug or feature request and mark it as 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

Mihai, the issue you linked was for Dasher accounts/domains. Looks like this is a regular consumer account.

Regardless, it seems that there's some issue with your machine where Chrome is failing to persist/read authorization tokens. You could try deleting your local profile data directories completely. Mihai - any other suggested steps?

The bug was for a dasher account, but the root cause was a problem with some Windows machine configuration (see comment https://bugs.chromium.org/p/chromium/issues/detail?id=744626#c29 ) and was not related to the account at all. From the comment on the other bug, it looks like "Chrome fails to store any sensitive data to disk (including these credentials, cookies, passwords etc.)."

@riclozcac.biz: Do you have any other problems with other sensitive data (do you have any issues with cookies / passwords being lost on restart?)

The problem is that this is due to some local machine configuration and it is impossible for me to debug. If you want to pursue this, it would be better to get some folks from the Windows team to look at this issue.