PS: It does not work, though Google Sync API keys are set up. It worked before without those keys. I can sign in from Chrome from the same machine with the same account.

What do you mean by you "cannot sign in"? What exactly happens, at each step?

Sorry, which steps?

As I tried to explain above … I’m entering my username/mail address, then my password, then two factor authentication key, I click ok, then sign in overlay window closes and nothing happens. I’m still not signed in. No message, no error, no warning, nothing.

Thank you!

Thank you for providing more feedback. Adding requester "shrike@chromium.org" for another review and adding "Needs-Review" label for tracking.

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

[mac triage] Perhaps some signin folks can help troubleshoot.

What are the states of your #show-material-design-user-menu and #enable-password-separated-signin-flow flags in chrome://flags?

I'm assuming your build comes from https://download-chromium.appspot.com/, is that correct?

The build you're using was missing some error reporting UI. This has landed now so if you update to the latest build you might get an error dialog if sign in fails. Can you try again with the latest build?

I just tried this on Mac with the latest Chrome canary build, 55.0.2883.0 (64 bit). I was able to login without any difficulties, with no unexpected behaviour. All my bookmarks, extensions and various settings sync immediately and without issue.

Now, this is on a machine with 10.11.6 El Capitan, not Sierra, so perhaps there's something going on there?

+erikchen@ who is more Mac-savvy than I am. ;-)

What are the states of your #show-material-design-user-menu and #enable-password-separated-signin-flow flags in chrome://flags?

“Default” on both.

I'm assuming your build comes from https://download-chromium.appspot.com/, is that correct?

Yes, installed via `brew cask install chromium --force --download` or manually …

The build you're using was missing some error reporting UI. This has landed now so if you update to the latest build you might get an error dialog if sign in fails. Can you try again with the latest build?

Unfortunately the same behavior again …

Thank you so far for your feedback!

I'm curious ... what happens if you open chrome and signin to a different account?

Signing in from chrome and canary works … signing in from chromium does not work with neither account. Hm.

Any new to this? I’d love to be able to use chromium again instead of canary.

With #show-material-design-user-menu and #enable-password-separated-signin-flow flags disabled in chrome://flags, I get "uh oh, service not available" …

Using version 56.0.2905.0 (64-bit) meanwhile …

Ok, that’s weird. When starting chromium from command line, I can sign in. Though, all menus have a very bold and blurry and pixelated type …

Starting chromium normal again says my login details are out of date and I have to sign in again. (Maybe, when chromium is started normally, my .bash_profile with the API keys is not read?)

This is the command line output.

```~ >> /Applications/Chromium.app/Contents/MacOS/Chromium
[94417:40963:1029/125741:ERROR:service_manager.cc(286)] Error: invalid Name: 19315F5363176EDC9C48725ADD61961D
[94467,3259311040:12:57:41.448628] Native Client module will be loaded at base address 0x00007ded00000000
[94417:775:1029/125804:ERROR:CONSOLE(1)] "Uncaught ReferenceError: inline is not defined", source:  (1)
[94417:40963:1029/125825:ERROR:ssl_client_socket_impl.cc(1081)] handshake failed; returned -1, SSL error code 1, net_error -100
[94417:775:1029/125828:ERROR:data_type_manager_impl.cc(34)] Bookmarks cryptographer error was encountered:
[94417:775:1029/125828:ERROR:data_type_manager_impl.cc(34)] Preferences cryptographer error was encountered:
[94417:775:1029/125828:ERROR:data_type_manager_impl.cc(34)] Typed URLs cryptographer error was encountered:
[94417:775:1029/125828:ERROR:data_type_manager_impl.cc(34)] Extensions cryptographer error was encountered:
[94417:775:1029/125828:ERROR:data_type_manager_impl.cc(34)] Search Engines cryptographer error was encountered:
[94417:775:1029/125828:ERROR:data_type_manager_impl.cc(34)] Sessions cryptographer error was encountered:
[94417:775:1029/125828:ERROR:data_type_manager_impl.cc(34)] Apps cryptographer error was encountered:
[94417:775:1029/125828:ERROR:data_type_manager_impl.cc(34)] App settings cryptographer error was encountered:
[94417:775:1029/125828:ERROR:data_type_manager_impl.cc(34)] Extension settings cryptographer error was encountered:
[94417:775:1029/125828:ERROR:data_type_manager_impl.cc(34)] Favicon Images cryptographer error was encountered:
[94417:775:1029/125828:ERROR:data_type_manager_impl.cc(34)] Favicon Tracking cryptographer error was encountered:
```

Neither does /etc/chrome_dev.conf work.

--Chrome Identity automated triaging--

This bug is Assigned and has gone one month without any activity, so it is being moved to Available to indicate that it is not actively being worked on. If you are working on this bug, please mark yourself as the owner and move back to Assigned. 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

Cleaning up sheriffbot label "Needs-Review" label as a part of modified "Needs-Feedback" sheriffbot rule. [ref bug for cleanup 684919]

I am also experiencing this issue on chromium 57.0.2987.133 from Arch Linux

I get as far as the two-fact auth pin. When I enter it, the dialog goes away, and chromium becomes completely unresponsive.

Interestingly, this only happens on my work machine and not my home machine. I cannot confirm right now if the versions are identical or not. Is there perhaps some missing dependency?

When run from the command line, it seems to hand here:
$ chromium
[818:818:0331/111217.712245:ERROR:child_thread_impl.cc(762)] Request for unknown Channel-associated interface: ui::mojom::GpuMain
[42:42:0331/111227.077858:ERROR:KeyboardEventManager.cpp(427)] Not implemented reached in static bool blink::KeyboardEventManager::currentCapsLockState()
[42:42:0331/111232.013529:ERROR:KeyboardEventManager.cpp(427)] Not implemented reached in static bool blink::KeyboardEventManager::currentCapsLockState()
[42:42:0331/111232.099782:ERROR:KeyboardEventManager.cpp(427)] Not implemented reached in static bool blink::KeyboardEventManager::currentCapsLockState()
[42:42:0331/111233.302513:ERROR:KeyboardEventManager.cpp(427)] Not implemented reached in static bool blink::KeyboardEventManager::currentCapsLockState()
[42:42:0331/111233.398352:ERROR:KeyboardEventManager.cpp(427)] Not implemented reached in static bool blink::KeyboardEventManager::currentCapsLockState()
[719:719:0331/111250.007733:ERROR:CONSOLE(1)] "Uncaught ReferenceError: inline is not defined", source:  (1)

I disabled #enable-password-separated-signin-flow in chrome://flags and was able to log in successfully.

If it matters, my sync information is passworded.

However, when trying to remove an extension after syncing, chrome hung exactly as it did during login. Lots of:

[8401:8401:0331/121903.146218:ERROR:background_mode_manager_aura.cc(13)] Not implemented reached in virtual void BackgroundModeManager::EnableLaunchOnStartup(bool)
[8401:8401:0331/121903.153086:ERROR:background_mode_manager_aura.cc(18)] Not implemented reached in virtual void BackgroundModeManager::DisplayClientInstalledNotification(const string16&)
[8401:8401:0331/121903.452170:ERROR:background_mode_manager_aura.cc(18)] Not implemented reached in virtual void BackgroundModeManager::DisplayClientInstalledNotification(const string16&)
[8401:8401:0331/121904.221361:ERROR:display_info_provider_aura.cc(31)] Not implemented reached in virtual void extensions::DisplayInfoProviderAura::UpdateDisplayUnitInfoForPlatform(const display::Display&, extensions::api::system_display::DisplayUnitInfo*)

This may be unrelated, or another bug, but the behavior was exactly the same as when I was failing to log in.

I have the exact same issue ( issue 811633 ). I can go through all of the steps of signing in as normal, but in the end I am not signed in (and still get the "you're missing out" prompts). No error occurs. 

If I enter the wrong password I still get an error. I can sign in to Google services separately--but the browser itself will not sign in. 

Escalating.

Not sure how many users this affects, but it seems like a potentially big sign-in problem/bug.

Triaging Signin bugs: Sabine, should I reassign this to Mihai or Jerome? This is marked as RB-Stable for M-66, so we don't have much time.

Sabine - can you please take a look at this with Mihai and Jerome and help triage?

aaronmgriffin@gmail.com: If this only happens on your work machine, this issue is most likely because Sync was disabled by enterprise policy. Is this plausible?
We are already working on a new UI for this case.

fooness@arcor.de: If this issue still exists, could you send us some screenshots of what you see when you open the user menu in the top right corner, or when you open chrome://settings? Thank you!

tom@ainscough.com: Could you please reproduce the bug, then open chrome://signin-internals and chrome://sync and send us screenshots of those pages (note that do have private info like email, so you may want to hash it before sending it out).

There is not much we can do until we get this information as we cannot repro it.

tangltom@chromium.org: The problem still exists. Please find the screenshots below.

Deleted: Screen Shot 2018-03-17 at 19.22.35.png 72.7 KB

	Screen Shot 2018-03-17 at 19.22.35.png 72.7 KB View Download

Deleted: Screen Shot 2018-03-17 at 19.22.53.png 49.8 KB

	Screen Shot 2018-03-17 at 19.22.53.png 49.8 KB View Download

Hi, I deleted all of my google-related cookies (literally everything with "google" in the name) then I went to:
https://chrome.google.com/sync
and reset the sync. 

Now I can sign-in on Mac and iOS! 

(In the past, I could not sign-in on Mac, Windows 10 or iPhone X either. I cannot test Windows 10 now because I'm currently out of the country.)

I cannot explain why I could not sign in on any device before, but now I can sign in on the iPhone X. I didn't change anything on the phone. That sync reset must reset something at google.com as well as locally. 

The solution to these sign-in issues seems to be to delete the cookies and reset the sync. Maybe the cookie deletion could be a little less drastic than I undertook. Alternatively, maybe just resetting the sync might have worked, but I didn't know about that until I deleted the cookies and went to chrome://signin-internals which showed that syncing had just been deauthorized as of today (I assumed by deleting its cookie), so I googled "chrome sync" and found https://chrome.google.com/sync where the problem was solved. 

Jerome, could you please take a look? Thanks!

Cookies should not affect in any ways signing in to Chrome.

I personally suspect this is an issue with the account that somehow entered an sync disabled state. This would mean that you would not be able to sign in and start syncing on any of your Chrome instances.
om@ainscough.com: Could you please confirm if that is the case?

This is not an iOS issue, and I do not think it should be blocking M66. Removing the labels.

It might very well be that it was an issue with the account. I just know what I did before it started working again. It could be that resetting the sync was enough, however, I don't know how to verify that.

I do not see how we can make progress on this bug anymore. I am going to close it for now. Please re-open if it happens again.