Tried to test this issue on chrome beta 69.0.3497.72 using Mac 10.13.6. Attaching screen-cast for reference.
NOTE:Unable to test this issue with GSuite and gmail (Gsuite asking for subscription while creating account)
Steps:
-----
1. Launched chrome
2. Signed into two gmail account and closed chrome and reopened 
As we are observed that two gmail accounts signed in

@Reporter: Could you please try this issue with fresh profile with out any extensions and aaps also test this issue with latest chrome beta 69.0.3497.72. Could you please upgrade to latest chrome stable 68.0.3440.106, you can download latest chrome builds here:" https://www.chromium.org/getting-involved/dev-channel ". Let us know whether issue still persists.

Thanks.!

Deleted: 879887.mp4 1.9 MB

	879887.mp4 1.9 MB View Download

After trying a bunch of different things, including switching back to "Classic gmail" (which did seem to resolve one of the issues), I disabled "Identity consistency between browser and cookie jar" flag in chrome://flags. Now I do not experience this problem, and also am able to choose the default Chrome account that I prefer.

Thank you for providing more feedback. Adding the requester to the cc list.

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

[+Services > SignIn]: looks like a sign-in issue.

From signin-internals screenshot in #1 it looks like primary account is in auth error state ("Invalid credentials (2)", where 2 = CREDENTIALS_REJECTED_BY_CLIENT). In the code I've backtracked it to DiceResponseHandler::ProcessDiceSignoutHeader, but I don't have enough familiarity with the logic there. David, can you please take a look?

Also, @Reporter: can you reproduce this on other machines/platforms?

I don't have easy access to another machine / platform, but will try.

Thank you for providing more feedback. Adding the requester to the cc list.

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

David, did you get a chance to look into this? It sounds like something is causing the user to be signed out of their Dasher account...could it just be that the token is expiring?

bsazonov (#8): CREDENTIALS_REJECTED_BY_CLIENT happens when the user revoke their Sync token by signing out on the web (i.e. logout from gmail).

So I would say that the accounts were removed and Sync stopped working because the user logged out of gmail.

Let me try to answer some questions:
1) Chrome will reorder the accounts at startup, so that the Sync account is the "default" google account. This is expected behavior.
2) Sync will stop working if the account is not signed in on the web (i.e. signed out from gmail).
3) Logging out one account of gmail will log out the other one as well

With that said, it seems that there is still an issue here, because accounts should not be logged out on restart automatically.

If there's some weird interaction between the latest version of Chrome and the new GMail interface, it would make some sense (perhaps) that you not seeing many reports of this (yet). I am somewhat early-adopted the new Gmail for both personal and work emails.

One thing you wrote confused me:

"3) Logging out one account of gmail will log out the other one as well"

For as long as I can remember, I can log out of my personal gmail and still stay logged into my work gmail and vice versa -- are you saying something different?

3) yes this is what I am saying. I don't think it was ever possible to logout selectively one account and not the others.

Ok, thanks -- I tried again and indeed you're right! Not sure what led to my confusion on that point. So indeed it narrows down this bug to just an unexpected logout. 

noah, can you please confirm that you're still getting signed out every time you restart Chrome? Can you also confirm that "Keep local data only until you quit the browser" in chrome://settings/content/cookies is turned OFF?

It happens still yes when that account consistency flag is enabled. And yes, "Keep local data only until you quit the browser" is off. I created a video here showing my reproduction of the issue, including the applicable settings:

https://www.youtube.com/watch?v=VO-PTqeDRTY

Hmmm, that is a little confusing. David, could you take a look at this bug using the video linked above? It has screenshots of signin-internals before and after restart.

Could this be another issue with decrypting the tokens loaded from disk during startup? noah - have you tried restarting your Mac and then reproducing the issue? Sometimes simply restarting your computer fixes the decryption issues caused by Keychain.

Since several weeks transpired between the initial report and that reproduction video, I'd be surprised (but it's definitely possible) if I hadn't done a restart. I'll try to reproduce again after a restart.

I was able to reproduce after a restart. Note that I have some extensions installed so it's not a pure test I guess. Sorry, the test is pretty disruptive to my workflow as is. 

I'm not sure if this is related but I'm on 70.0.3538.45, with the flag #account-consistency disabled. I ran into an issue where Chrome will change my default account on Google sites to the account I'm using to sync with Chrome.

I have a case where I want to sync my Chrome data with account B but on google sites I want account A as the "default" account (i.e. authuser=0).

I first cleared all my cookies, logging out of all my accounts. I login with Account A through https://www.google.ca/. Then I login with Account B through https://www.google.ca/. Now, Account A should be Default, Account B is secondary (authuser=1). I setup my Chrome sync with Account B. I did this yesterday.

So today after opening Chrome, somehow my default account on Google sites (google.ca, gmail, etc.) changed to Account B. And Account A is authuser=1. My Chrome sync account is still Account B. I don't want Chrome to change the order of my logged in accounts on Google sites.

#23: this is expected behavior. We don't support having account A as first account in google.ca and account B in Sync. Accounts are re-ordered on startup to enforce this.

#24: Thanks for the video. It's very clear and contains a lot of information.

Here is what I understand, from a signin perspective.

0. Dice is enabled.
1. User starts with Sync paused, and there is no Google cookie.
2. User adds a non-sync account as default google account.
3. User adds the sync account as a secondary google account. Sync is fixed.
4. Restart Chrome
5. All accounts are gone despite the DB being loaded successfully. Sync is back to paused. 

After restart, I also see "Token revoked" events in signin-internal. I'll try to understand what could be causing these. 

I tried to repro this exact scenario (although on linux and on trunk), and it did not happen for me.

#24: There are discussions to change this, see https://bugs.chromium.org/p/chromium/issues/detail?id=889366

I hope these changes are reverted or an option is created to do so.

#24

The steps you listed are exactly what I do (I prefer my non-sync account to be default at work).

With the latest update to 70.0.3538.77 I started experiencing the accounts being logged out on browser restart; before it just automatically switched my sync account to default (not sure which was more annoying!)

droger@: triage ping, is there any status update? Thanks!