Auth v6 - Sign-in - Invalid phone number format.

[hanoj-budime]

Before opening, please confirm:

• I have searched for duplicate or closed issues and discussions.
• I have read the guide for submitting bug reports.
• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

JavaScript Framework

React

Amplify APIs

Authentication

Amplify Version

v6

Amplify Categories

auth

Backend

None

Environment information

....

Describe the bug

Amplify checks phone_number is required during / once user migrated ?

During user migration required phone_number which is missing but user is mirgrated succesfully from one pool to other pool.
However sign-in failed with InvalidParameterException ( Invalid phone number format. )

Expected behavior

Amplify must improve nextstep like CONFIRM_SIGN_IN_WITH_REQUIRED ( where in-case phone_number will be required for MFA sign-in )

Reproduction steps

1. auth v6.5
2. User Mirgation from old-pool to new-pool
3. In old-pool phone_number is not required.
4. In new-pool phobe_number is required ( for MFA sign-in ) .

Code Snippet

// Put your code below this line.

Log output

// Put your logs below this line

aws-exports.js

No response

Manual configuration

No response

Additional configuration

No response

Mobile Device

No response

Mobile Operating System

No response

Mobile Browser

No response

Mobile Browser Version

No response

Additional information and screenshots

No response

[cwomack]

Hello, @hanoj-budime 👋. Is this happening after upgrading from v5 of Amplify to v6? I believe this is the error you'd experience if you're trying to call the newer API using the Auth.confirmSignIn() parameters. If so, there are changes to the confirmSignIn() parameters to include an object with a challengeResponse property rather than separate ones for user and code (like in v5). More information on the differences can be found here in the docs.

Can you see if calling the API like shown below helps resolve the issue?

await confirmSignIn({ challengeResponse: "123456" });

[hanoj-budime]

@cwomack

Amplify checks phone_number is required during user migrated ?

During user migration required phone_number which is missing but user is mirgrated succesfully from one pool to other pool.
However sign-in failed with InvalidParameterException ( Invalid phone number format. )

error at

  await signIn({ username, password, options });

[israx]

hello @hanoj-budime. Sorry for any inconvenience using the library.

The Invalid phone number format error message is due to providing an incorrect phone_number format either during signUp or signIn.

Bad:
signIn({username:"9990009999", password:*****}

Good:
signIn({username:"+19990009999", password:*****}

Also, are both of your user pools configured to login with phone_number, or/and do they require a phone_number attribute during signUp?

[cwomack]

@hanoj-budime, wanted to check in and see if @israx's comment above helped unblock you or if you're still experiencing this. The Cognito docs on the phone_number attribute go into a little more detail about the necessary formats that are critical for user pools. Let us know if this helps clear things up!

[cwomack]

Closing this issue as we have not heard back from you. If you are still experiencing this, please feel free to reply back and provide any information previously requested and we'd be happy to re-open the issue.

Thank you!