Authenticator should show better error message when code in typed incorrectly too many times on Password reset

[pmellaaho]

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
authenticatorVersion = "1.2.1"

Environment information

# Put output below this line
Gradle 8.7

Please include any relevant guides or documentation you're referencing

No response

Describe the bug

On reset password use case, if the user keeps inserting the code incorrectly the Authenticator will show "Code is incorrect" for the first five times (CodeMismatchException). After that the Authenticator is showing generic "Sorry, something went wrong" -message to the user. This happens because Authenticator does not have specific handling for LimitExceededException which is received after fifth attempt. Better error message to show would be e.g. “Too many attempts, try again later”

Reproduction steps (if applicable)

No response

Code Snippet

// Put your code below this line.

Log output

// Put your logs below this line
Encountered AuthException: LimitExceededException{message=Number of allowed operation has exceeded., cause=LimitExceededException(message=Attempt limit exceeded, please try after some time.), recoverySuggestion=Please wait a while before re-attempting or increase the service limit.}

amplifyconfiguration.json

No response

Additional information and screenshots

No response

[mattcreaser]

Thanks for posting this @pmellaaho. We should have specific handling for this scenario.

I also believe we should add general-purpose error message handling like there is on the Swift Authenticator where you can specify the string content for arbitrary exception types. I'll open that as a separate feature request.

[mattcreaser]

Please see feature request #181

[mattcreaser]

This was release in Authenticator 1.3.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.