Closed lawmicha closed 5 months ago
This issue was opened by a maintainer of this repository; updates will be posted here. If you are also experiencing this issue, please comment here with any relevant information so that we're aware and can prioritize accordingly.
Confirmed that without the pre-sign up auto confirm user lambda, then the flow from sign up -> confirm -> sign in works as expected. We also confirmed that the state is being updated here, https://github.com/aws-amplify/amplify-ui-swift-authenticator/blob/main/Sources/Authenticator/States/SignUpState.swift#L57 credentials.username
is being set to the email value. This does not appear to be a Gen2 related bug
Yes, this is an Authenticator bug when a new user is automatically confirmed, the component attempts to log in without the credentials and it causes the error. I will submit a fix.
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. If you wish to keep having a conversation with other community members under this issue feel free to do so.
I have the following backend CDK
amplify/auth/resource.ts
amplify/auth/pre-sign-up-handler.ts
When I use Authenticator to sign up with email, the user gets auto confirmed by the lambda, and Authenticator attempts to sign in the user.
The sign in fails