[Authenticator] User can maybe see an empty verification attribute screen

[mattcreaser]

Before creating a new issue, please confirm:

• I have searched for duplicate or closed issues.
• I have read the guide for submitting bug reports.

Which UI component?

Authenticator

Gradle script dependencies

// Put output below this line

Environment information

# Put output below this line

Please include any relevant guides or documentation you're referencing

No response

Describe the bug

If the configuration file contains one verification mechanism and a user doesn't have a matching attribute for that mechanism, we still show the attribute verification screen, but the list is empty.

It's unclear if this is a valid scenario - I tried updating my Cognito console to require a different verification mechanism but my amplifyconfiguration.json did not change on amplify pull. Although it's not clear whether a user can actually get into this situation, we should still guard against this possibility.

This can be fixed by adding a condition for verificationAttributes.isEmpty() here.

Reproduction steps (if applicable)

1. Setup Cognito with Email as a verification attribute and don't make phone numbers required.
2. Create a user.
3. Change verificationMechanisms in amplifyconfiguration.json to be "SMS".
4. Log in as that user.

Code Snippet

// Put your code below this line.

Log output

// Put your logs below this line

amplifyconfiguration.json

No response

Additional information and screenshots

No response

[mattcreaser]

This was released in Authenticator 1.2.0

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.