Can you post screenshots of

chrome://sync-internals/
chrome://signin-internals/
chrome://sync-internals/

You said this is across all your devices, what kind of devices? All Windows?

Are you friends/family able to sign into your devices with their accounts? Or maybe if you made a new google account, does that work?

Yes, all devices.

I have android and windows, but I am not able to sign in anywhere from any platform.

Yes they are.

I have not tried to make a new account because I need this one.

Deleted: sign.PNG 23.9 KB

	sign.PNG 23.9 KB View Download

Deleted: sync.PNG 79.6 KB

	sync.PNG 79.6 KB View Download

In regard to what kind of devices I have a tablet, laptop, stationary and a phone.

I also tried to sign in on me previous phone and tablet, but no luck.

Hey signin folks, can someone take a look at this? I'm not sure how to proceed.

Re-tested the issue again and unable to reproduce the issue on Windows 7, Mac OS 10.12.6 and Ubuntu 14.04 using the latest Canary 63.0.3223.0 and latest Stable 61.0.3163.100 with the below steps.

1. Launched Chrome and clicked on Sign into Chrome button.
2. Entered Email ID and password and can clicked on Ok,Got it button to sync everything.
3. Can observe that all the bookmarks, history etc are synced to the google account and no issues are observed.

Please find the attached screen-cast for reference.

Can someone from Services>SignIn team please look into this issue and help in further triaging?

Thanks..

Deleted: 767129.webm 3.1 MB

	767129.webm 3.1 MB View Download

Mihai, could you look into this? It seems like a sign-in issue rather than a sync issue.

steffen.elgaard@: From chrome://signin-internals It looks like you do not have account in the token service, this pretty much means that sign-in will not work for you.

May I ask you to to the following:
1. Go thorough a Chrome sign-in flow (from settings). Follow the movie at comment #7.
2. At the end of the sign-in flow, do you see the confirmation dialog with title "You've signed in and turned on Sync" (as in movie at comment #7, at 0:19).

Possible outcomes:
a) If you do, then you should be signed in and syncing after you click the "OK, Got it" button. If you are not, please take a screenshot of chrome://signin-internals (without closing the browser).
b). If you do not, then you are not signed in to Chrome (and sync will not work). In this case, what I suppose happens is that Chrome fails to add the account to your Google authentication cookies (which is the last step in the Chrome sign-in flow).

Please let me if you end up in a) or b) above.

--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

 Issue 774128  has been merged into this issue.

I get b.

All the information I have is in this video.

I have tried to reset to default.

The same issue occur.

Thank you for providing more feedback. Adding requester "ranjitkan@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

This is indeed a very strange bug. To sum up the behavior from the bug:
1. [Good] Chrome gets an auth token
2. [Good] Chrome manages to add it to the token service and to the Gaia cookie
3. [Good] Chrome shows the sync confirmation dialog

At this point, Chrome starts to go crazy: 
4. [Strange] Chrome sync stops.
5. [Strange] Seems like the account is simply removed from Chrome. From the screenshots sent earlier, 

It also looks like this is related to the account that is being used:
* other accounts seem to be able to sign in on the same machine
* same account fails to sign on on other devices

The problem is that it is hard to explain why this happens as we have multiple points that force a sign-out (sync dashboard was reset, sign-in preference changed etc). I think we would need additional info.

May I ask you to do the following:
* Run the same test as in video above
* Open chrome://histograms/
* On this page search for "Histogram: Signin.SignoutProfile"
* Copy-paste in this bug what you see there for this histogram.

Histogram: Signin.SignoutProfile recorded 2 samples, mean = 5.0 (flags = 0x41)
0  ... 
5  ------------------------------------------------------------------------O (2 = 100.0%) {0.0%}
6  ... 

This should be it.

I really appreciate the help.

Thank you for providing more feedback. Adding requester "msarda@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

skym: do you know what could be causing SERVER_FORCED_DISABLE on the Sync side?

Adding back the Needs-Feeback label for checking about:flags, as described below/

FYI: that histogram sample has the following descriptions:
// The sync server caused the profile to be signed out.
SERVER_FORCED_DISABLE,


Looking at the code, this is used in two places:

1) https://cs.chromium.org/chromium/src/chrome/browser/signin/dice_response_handler.cc?rcl=5818fa1c113533a8eabaaa7311b2ffec3c446d2e&l=324

This can only happen if the "Dice" feature is enabled. I'm not sure it exists in Chrome 61 though. Can you go to about:flags and check if there is a feature called "Identity Consistency". If there is one, please change its value back to Default and that will probably fix your problem. 

2) https://cs.chromium.org/chromium/src/components/browser_sync/profile_sync_service.cc?rcl=5818fa1c113533a8eabaaa7311b2ffec3c446d2e&l=1124

I'm not familiar with this. CC'ing skym@ who probably knows more.

As a side question: I wonder if it is right to collapse these two events into the one SERVER_FORCED_DISABLE value. Maybe these should be separate values.

Do you need any information from me at the moment, or am I on standby from the time being?

Thank you for providing more feedback. Adding requester "droger@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

Can you check about:flags as described in comment 22?

I am having a hard time figuring out what I am instructed to do in comment 22.

If you could rephrase it, so I might be able to understand what is needed of me, I would gladly oblige.

Sure.

Type "about:flags" in the url bar.
This should open a page talking about experiments.

Look for an experiment called:
"Identity consistency between browser and cookie jar"

There will be a small box below with the value of the experiment.
Please check that the value here is "Default". If this is not "Default", let me know what it was, and try changing it back to Default.

You can probably use this URL to find the experiment:
chrome://flags/#account-consistency

It is set to default and it was set to default when i typed chrome://flags/#account-consistency

Deleted: Capture.PNG 16.7 KB

	Capture.PNG 16.7 KB View Download

Thanks, so this rules out option 1 from comment 22, and leaves only option 2.
skym: do you know what could be causing the SERVER_FORCED_DISABLE (see comment #22)?

Looking at the video, you can see the error type on sync-internals is NOT_MY_BIRTHDAY. There's some sort of server side data inconsistency that's causing this.

I believe there was some race condition a while ago where you could get into a situation where the server's two data stores disagreed with what the accounts birthday was, but I believe it was fixed a few months ago. Reading your initial description that this has been an ongoing problem for a while makes me think that you got into this situation when we had this bug.

If you just clear your server data again, through https://chrome.google.com/sync , it should fix the problem immediately. If it doesn't, let us know.

Eureka!

I FINALLY worked!

Thank you so much for the help!

Cheers. 

Ah that's right, I'd totally forgotten about that sync bug. Thanks for chiming in, Sky!

Glad that everything is working again.