AmplifyAuthenticator - Verify Contact Information Screen displays "[e-mail]"

Describe the bug After federated sign in, the verify contact information screen displays “[e-mail]” as the email address for verification

To Reproduce Steps to reproduce the behavior:

1. Go to https://master.dw8p5s05jola3.amplifyapp.com/
2. Sign in using an external IdP (Google for example)
3. You will see an “Account recovery requires verified contact information” screen (screenshot below)

Expected behavior This screen did not previously show up after federated sign in, so I am not sure the exact expected behavior. I found this issue https://github.com/aws-amplify/amplify-js/issues/6481 and this PR https://github.com/aws-amplify/amplify-js/pull/6508, so looks like this is verification screen is intended. However I think either “Email” or the users actual email address should show up as the option to select.

Code Snippet Full code is here for those who have access

  <AmplifyAuthenticator usernameAlias="email" style={{ textAlign: 'center' }}>
            <AmplifyForgotPassword
              usernameAlias="email"
              slot="forgot-password"
              formFields={[
                {
                  type: "email",
                  required: true,
                },
              ]}></AmplifyForgotPassword>
            <AmplifySignIn
              usernameAlias="email"
              slot="sign-in"
              formFields={[
                {
                  type: "email",
                  required: true,
                },
                {
                  type: "password",
                  required: true,
                }
              ]}></AmplifySignIn>
            <AmplifySignUp
              usernameAlias="email"
              slot="sign-up"
              formFields={[
                {
                  type: "email",
                  required: true,
                },
                {
                  type: "password",
                  required: true,
                },
                {
                  type: "phone_number",
                  required: false,
                },
                {
                  type: "locale",
                  value: this.state.lang,
                  inputProps: {
                    type: 'hidden',
                  }
                }
              ]}></AmplifySignUp>
            <div>
              {I18n.get("WAIT_REDIRECTION")}
              <AmplifySignOut />
            </div>
          </AmplifyAuthenticator>

Screenshots

Environment

  System:
    OS: macOS 10.15.6
    CPU: (8) x64 Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz
    Memory: 59.58 MB / 8.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 12.18.0 - /usr/local/bin/node
    npm: 6.14.8 - /usr/local/bin/npm
  Browsers:
    Firefox: 68.8.0
    Safari: 13.1.2
  npmPackages:
    @aws-amplify/ui-react: ^0.2.15 => 0.2.15 
    @testing-library/jest-dom: ^5.11.4 => 5.11.4 
    @testing-library/react: ^10.4.9 => 10.4.9 
    @testing-library/user-event: ^12.1.3 => 12.1.3 
    aws-amplify: ^3.0.24 => 3.0.24 
    axios: ^0.20.0 => 0.20.0 
    jwt-decode: ^2.2.0 => 2.2.0 
    react: ^16.13.1 => 16.13.1 
    react-app-rewired: ^2.1.6 => 2.1.6 
    react-dom: ^16.13.1 => 16.13.1 
    react-router-dom: ^5.2.0 => 5.2.0 
    react-scripts: 3.4.3 => 3.4.3 
  npmGlobalPackages:
    @aws-amplify/cli: 4.28.1
    ask-cli: 2.13.0
    nodemon: 2.0.4
    npm: 6.14.8
    serve: 11.3.2
    serverless: 1.73.1

[eddiekeller]

It shouldn’t! Federated sign in flows through its own logic path in our state machine, so it really shouldn’t ever transition to that “verify” screen. I’ve included a video showing the federated behavior on the new authenticator. Closing this issue since this is fixed in the new version of the authenticator and you aren’t working with amplify anymore.

https://user-images.githubusercontent.com/17255334/138963603-477c9181-7f17-4604-acf0-b66ae8dbcb38.mov

[ericclemmons]

Confirmed that this behavior exists and is undesirable.

1. Clicking “Sign in with Google”

   

2. After the redirect, I’m prompted to verify my email:

   

3. However, when refreshing the page, I get the desired experience: