Chrome Sync breaks OAuth flows for additional Google accounts

[max-bb]

This is possibly a browser bug, or unintentional side effect, but when chrome sync is enabled, the OAuth flow breaks badly for non-system google accounts.

It is common for users of our app to wish to sign into google accounts that are not their primary system accounts. To facilitate this, as part of our sign in flow, we set the login hint.

If the user is not signed into Chrome/Chrome Sync, they then get a flow which is very similar to what used to happen in an embedded WebView. They get a screen with their email pre filled in, and a next button, and can then enter their password. This works great.

If the user IS logged into chrome/chrome sync, then they get a flow where their OAuth accounts are tied into their Google System Accounts. The login hint is no where to be seen, and they can only choose a system account, or add a new system account (having to enter in their google account details all over again, and then getting irrelevant questions about payments as well), pulling in a lot of functionality and data they did not intend to add.

Is there anyway to bypass Chrome Sign In? It works great if the user wants to add their primary system account, but completely interrupts the flows for additional accounts, and may be completely impossible for novice users to navigate at all.

[max-bb]

This is similar to #173, but is more focused on the 'system integration' aspect being problematic.

[iainmcgin]

This is the same issue as #173 and #172. I've been discussing this with the Chrome team, we have not reached consensus on a fix yet.

[max-bb]

Thank you. I wanted to capture the problem more concisely as the root cause is the same as #172 and #173 but the outcome is a bit different, and as we all know, the deadline is looming :)

[lquinn]

@WilliamDenniss, would it be possible to push out the April 20 deadline mentioned at https://developers.googleblog.com/2016/08/modernizing-oauth-interactions-in-native-apps.html until we can resolve issues like #172, #173, and this one? I'm very worried about the user experience with these issues.

[awhlee]

Is there an update to this? we are having the same problem. are people reverting back to using a webview within their app?

[iainmcgin]

Work is underway to fix the issue in Chrome, I don't have an ETA from the team yet.

[chrisstj]

Hi.
I am having the same issue when adding more than one account, the account that was added first is logged in again and the login page is being bypassed.
Even with the Samsung Internet Browser and Opera Browser I have the same issue.
It doesn't matter if it is the first time setup for all browsers or already synced with google accounts.

Best regards,
Chris