dk

On device storage is important for all above use cases mentioned. In context of a cross-platform application, if all platforms cannot support a unified offline storage system it will become...

> Hi @dkliss, good question, the observed behavior is expected when using `Amplify.Auth.verifyTotpSetup()`. > > The correct API to call while onboarding a User to MFA is `Amplify.Auth.confirmSignIn(confirmationValue: totpCode)`. >...

> Hi @dkliss, I looked into it further and it does actually appear to be a bug. Thank you for the extra context with your use case as it helped...

Hi @Equartey, thanks for the update. I tried below but I received **no exception** such as "Code Mismatch" when I enter any incorrect code. With correct code, TOTP is setup...

> Hi @dkliss, we catch the exception internally, but allow multiple calls to `verifyTotpSetup` without the need to restart setup. > > I suspect the problem you're facing is not...

> Hi @dkliss, I have a work around for you in the meantime. > > When setting up a user's TOTP for the first time, you can check the user's...

Hi @Equartey Thanks you for response. I verified this and I received exception as expected. Much appreciate your help on this throughout.

> Hello - I attempted to reproduce the issue you are experiencing on Android and iOS and cannot reproduce it. I do see the break point hit. I have a...

> @dkliss - I am fairly certain this is caused by [flutter/flutter#141882](https://github.com/flutter/flutter/issues/141882), which has been resolved in flutter master. I can reproduce this with Flutter v3.16, but cannot reproduce this...

> The social provider page is not pushed on top of your app. The browser redirects to the social providers url. That is, from `localhost:3000` to `myaccounts.google.com` (for Google sign...