Elijah Quartey

@filipesbragio thanks for the extra data point. It appears iOS is dropping properties set to a `null` literal when making the request to AppSync. The work around would be to...

Hi @harrynguyen2510, I understand you're seeing inconsistent ordering of messages in your app. It's unclear to me how you are sorting them. What value you are sorting by? By what...

Hi @osehmathias, could you please provide more context about your use case?

Hi @osehmathias, appreciate the extra context. If you're looking to change the selective sync during runtime, checkout this guide: https://docs.amplify.aws/flutter/build-a-backend/more-features/datastore/sync-to-cloud/#reevaluate-expressions-at-runtime

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)`. If the code is...

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 narrow...

Hi @dkliss this has been fixed in `amplify_auth_cognito: ^1.7.1`. I'm going to close this issue as complete, please reach out if you encounter another issue.

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 receiving enough feedback...

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 MFA preference to...

Hi @dkliss, I appreciate the discussion so far. It's been helpful for me to understand your use case. I've opened https://github.com/aws-amplify/amplify-flutter/pull/4558 to throw an exception during TOTP setup. Will update...