Skip to content
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

[Auth] Lambda trigger exception not forwarded when using social sign-in #1649

Closed
1 task done
dnys1 opened this issue Feb 1, 2022 · 4 comments
Closed
1 task done
Assignees
Labels
auth Related to the Auth category/plugins flutter Calling Amplify Android via the Flutter facade improvement Any improvement that's not a bug and not requesting new functionality

Comments

@dnys1
Copy link
Contributor

dnys1 commented Feb 1, 2022

Before opening, please confirm:

Language and Async Model

Kotlin

Amplify Categories

Authentication

Gradle script dependencies

implementation 'com.amplifyframework:aws-auth-cognito:1.28.3-rc'

Environment information

N/A

Please include any relevant guides or documentation you're referencing

No response

Describe the bug

aws-amplify/amplify-flutter#1279

CX is not receiving exception message from Lambda trigger when using social sign-in. I was able to reproduce when using social sign-in only - regular sign-up and Hosted UI both returned the exception.

Is this expected behavior? And is there a way to expose these exceptions?

Reproduction steps (if applicable)

  1. Set up lambda trigger which throws an exception (I tested with pre-signup).
  2. Set up social sign-in (I tested with Google).
  3. Sign in with social login
  4. Receive generic error message w/out Lambda exception.

Code Snippet

// Put your code below this line.

Log output

// Put your logs below this line


amplifyconfiguration.json

No response

GraphQL Schema

// Put your schema below this line

Additional information and screenshots

No response

@tjleing tjleing added auth Related to the Auth category/plugins flutter Calling Amplify Android via the Flutter facade improvement Any improvement that's not a bug and not requesting new functionality labels Feb 1, 2022
@Sunsiha
Copy link

Sunsiha commented Feb 22, 2022

any update on this?

@eeatonaws
Copy link
Contributor

Thank you for reporting this issue. I was able to reproduce the issue and am looking into a fix.

@eeatonaws
Copy link
Contributor

A fix for the issue has been released in Amplify Android 1.37.4.

@github-actions
Copy link
Contributor

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auth Related to the Auth category/plugins flutter Calling Amplify Android via the Flutter facade improvement Any improvement that's not a bug and not requesting new functionality
Projects
None yet
Development

No branches or pull requests

4 participants