-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix parameters in sendMFASelectionAnswer #6418
Conversation
Codecov Report
@@ Coverage Diff @@
## main #6418 +/- ##
=======================================
Coverage 73.23% 73.23%
=======================================
Files 208 208
Lines 12941 12941
Branches 2529 2529
=======================================
Hits 9477 9477
Misses 3272 3272
Partials 192 192 Continue to review full report at Codecov.
|
@donaldpipowitch Can you share some sample code on how you're using Thanks! |
If you search for those params in the file you'll see that the API returns |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix @donaldpipowitch! This does appear to be a bug, as it uses the correct key name in other responses in the same file, as you showed with your screenshot. Also, the documentation shows the correct casing as ChallengeName
/ChallengeParameters
.
This pull request has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
The wrong parameters were passed to the callbacks of
sendMFASelectionAnswer
.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.