Not redirected to RedirectUriReceiverActivity when adding a new account

[ashray-aw]

Hello,

This issue happens on
Chrome version : 56.0.2924.87
AppAuth version :0.5.0
Nexus 5(Android version : 6.0.1)

This happens in the demo app included in the lib too

Here are the reproductions steps :

• Sign into chrome with a test account, say - test1@gmail.com
• Now try to sign in to AppAuth Demo with another test account : test2@gmail.com(This account should have never been configured on chrome or the device before)
• Notice that after account authentication the user is directed to the Chrome browser's default home page while it should have returned to the InitializingActivity/the-activity-that-launched-AuthorizationManagementActivity and stays there
• So now the user has to manually back out of the app all the way to get back to the demo app.

This same behavior is not observed if test2@gmail.com were already authenticated on the device before. In which case, the user is taken to the "Allow/Deny-permissions screen" and once the user allows the action, RedirectUriReceiverActivity is launched which eventually launches the InitializingActivity.
This also does not happen if test2@gmail.com were the first account to be configured on chrome

This is the intent filter on RedirectUriReceiverActivity

<intent-filter>
  <action android:name="android.intent.action.VIEW"/>
  <category android:name="android.intent.category.DEFAULT"/>
  <category android:name="android.intent.category.BROWSABLE"/>
  <data android:scheme="com.googleusercontent.apps.<CLIENT-ID>" />
</intent-filter>
<!-- Release redirect URL -->
<intent-filter>
  <action android:name="android.intent.action.VIEW"/>
  <category android:name="android.intent.category.DEFAULT"/>
  <category android:name="android.intent.category.BROWSABLE"/>
  <data android:scheme="com.googleusercontent.apps.<CLIENT_ID>" />
</intent-filter>

Please let me know if any other details are required.
Thanks

[iainmcgin]

This appears to be an issue with Google's authorization endpoint on Chrome - Google is now trying to enforce better consistency between the accounts signed in to your device, Chrome and the content area. When I try this on my device, I am pushed to Android list of Google accounts and must add the account there. I am not all that surprised that this results in a loss of context for the authorization operation when you return to the app.

I'll flag this to the Chrome / Android account people. I don't know what the right solution should be.

[iainmcgin]

Related to #172.

[ashray-aw]

Thank You @iainmcgin.

[shafty023]

I too am having this same issue with the same repro steps. Let me know if you need any further info from me as well.