VerifyContact "Neither Email nor Phone Number selected" with Email selected
See original GitHub issueDescribe the bug When using aws cli or aws console to create a user in cognito, the verify contact process in amplify is buggy. “Email” is showing as the selected item in the select. The “Verify” button is disabled. The work around is to select “Phone Number” then select “Email” again.
To Reproduce Steps to reproduce the behavior:
- Create sample React Native application using CRNA wrapped in Expo and Amplify
- Create user with AWS cli (see below for command)
- Run expo start (I presume this also fails regardless how you’re emulating the application)
- Log in with username/temp pwd from cli command
- You should see the Verify Contact screen with “Email” as the selected input
- See that the Verify contact button is disabled.
Expected behavior Verify should not be disabled b/c Email is the selected item. I would like to import my users with cli and provide them temp password so that they can log in and verify their account.
Desktop (please complete the following information):
- OS: Windows 10
- Browser N/A (this occurs on React Native)
- Version 28
Smartphone (please complete the following information):
- Device: Moto G5
- OS: Android 8
Additional context In VerifyContact.js, I prevented the verify button from being disabled. Pressing verify shows that “Neither Email nor Phone Number selected” error message (even though “Email” is shown).
package.json
- “aws-amplify”: “^1.1.19”,
- “aws-amplify-react-native”: “^2.1.7”,
- “expo”: “^32.0.0”,
- “expokit”: “^32.0.7”,
- “react”: “16.5.0”,
- “react-native”: “https://github.com/expo/react-native/archive/sdk-32.0.0.tar.gz”,
Sample code
cli command used to create users: aws cognito-idp admin-create-user --user-pool-id us-west-abcdefg --username User1 --temporary-password 1111 --user-attributes=Name=email,Value=email@emal.com,Name=phone_number,Value="+15555555555"
Issue Analytics
- State:
- Created 4 years ago
- Comments:6
Top GitHub Comments
This issue has been automatically closed because of inactivity. Please open a new issue if are still encountering problems.
This is still a bug, automatically closed by a bot or not.