When we are getting support for EMAIL_OTP challengeName, email MFA?

[gurindertrantor]

Is this related to a new or existing framework?

No response

Is this related to a new or existing API?

No response

Is this related to another service?

No response

Describe the feature you'd like to request

MFA for email was introduced by Cognito but Amplify doesn't provide support for this particular challenge name.

Describe the solution you'd like

Ideally it should support email MFA by default as it support MFA for phone number.

Describe alternatives you've considered

Ideally it should support email MFA by default as it support MFA for phone number.

Additional context

No response

Is this something that you'd be interested in working on?

• [ ] 👋 I may be able to implement this feature request
• [ ] ⚠️ This feature might incur a breaking change

[cwomack]

Hello, @gurindertrantor 👋 and thanks for opening this issue. Yes, we are definitely tracking this on our side and already have a feature branch (with associated PR's) that is in the works at this point. We'll update this issue as progress is made and keep anyone following informed when it's merged. Thanks!

[gurindertrantor]

Hi @cwomack and @jjarvisp any update on this? Is there any expected timeline?

Thanks!

[Mehdi-android]

Hi @cwomack and @jjarvisp what is the update? I am using this library in android kotlin implementation("com.amplifyframework:core:1.28.0") implementation("com.amplifyframework:aws-auth-cognito:1.28.0")

I am getting error
AuthException{message=Sign in failed, cause=java.lang.IllegalArgumentException: No enum constant com.amazonaws.mobile.client.results.SignInState.EMAIL_OTP, recoverySuggestion=See attached exception for more details.}

Give timeline please, when can we expect this issue to be resolved?

Thanks!