WelcomeBackIDPPrompt cancels sign in prematurely

[SUPERCILEX]

While working on #349, I ran into an interesting issue that I'm pretty sure affect all users of 0.6.0. Here was the config I ran with:

• Android device: 6P
• Android OS version: 7.0
• Google Play Services version: 9.6.83

Here's some debugging:

I haven't had time to look into this issue in great detail, but mIdpProvider ends up being null because of providerParcel disagreeing with mProviderId about what the provider is. BTW, tests are happy.

BTW: I disabled smart lock, started AuthUI with only the email provider, and here is my existing user:

[SUPERCILEX]

I figured out why this stuff is happening: if the Smart Lock credential saved is from Google (or any other provider), but the AuthUI flow doesn't enable that provider, this issue happens. I don't know if this needs to be fixed since people will normally stick with the same providers if they are calling the auth flow from different places in their app.

[SUPERCILEX]

I discovered another bug related to this issue: if you enable smart lock and save a credential, sign out and then start the auth flow again without enabling smart lock, the blue bar showing the smart lock info still shows up and the user is not signed in (that bit is expected behavior, but the blue bar at the bottom is not).

[SUPERCILEX]

I don't know why it didn't close itself, fixed in #357.

[samtstern]

@SUPERCILEX I like to keep things open and "fix-implemented" until they've actually been released, otherwise people get confused why they're still experiencing "closed" bugs

[SUPERCILEX]

Sounds good!

[samtstern]

The fix for this issue has been released in version 1.0.1.