Hi Krishna,
Could you help us debug this issue ?

Also Disabling "Enable new gaia password-separated sign in flow" in chrome://flags is a possible workaround

Ligi, could you pls try to repro and bisect if possible. Thank you.

Jim here, my users uncovered this bug. Workaround of chrome://chrome-signin/?access_point=0&reason=0 is beginning to fail. Update please?

Hello team, does someone have an update on this issue?
I have another customer reporting this situation, I found two solid workarounds:

1- Sign in through the URL chrome:chrome-sign-in (Instead clicking on Settings and sign in)

2- Disabling the flag: #enable-password-separated-signin-flow (By disabling this flag the issue cannot be reproduce no matter which URL is used to log in, it will always be a successful log in.

1) jsantacruz - please make sure your cases are tagged correctly. Please check if the issue is still happening

2)  Mzheng - could you please help us test this please ?

Unable to reproduce this issue on Windows 10 with chrome #58.0.3029.110, #60.0.3112.101, as per steps mentioned in the comment #0

Attaching the screen-cast for reference.

marcore@ Could you please look into it and let is know any steps i have missed while reproducing the scenario

Deleted: 721380-1.mp4 1.4 MB

	721380-1.mp4 1.4 MB View Download

Just to Update, 
Unable to reproduce this issue on windows 7 with chrome #60.0.3112.101

Re-assign to yanglee@.

Ligi and Yang, PTAL and see if this a non-repro?  Thanks.

Greetings,

The problem continues, this impacts our business processes and makes it difficult to assure our users that we can consistently deliver their profiles to them as it does for their consumer accounts in Chrome, Firefox, Internet Explorer. Are there any steps I can take to escalate this? I can make myself available for a Hang Out session if needed.

Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Wednesday, 12/19/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!

Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.