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

Missing attributes after recreating account using a social provider #13431

Closed
2 tasks done
steptro opened this issue Nov 26, 2023 · 4 comments
Closed
2 tasks done

Missing attributes after recreating account using a social provider #13431

steptro opened this issue Nov 26, 2023 · 4 comments
Labels
auth Issues tied to the auth category of the CLI pending-response Issue is pending response from the issue author pending-triage Issue is pending triage

Comments

@steptro
Copy link

steptro commented Nov 26, 2023

How did you install the Amplify CLI?

curl

If applicable, what version of Node.js are you using?

v18.16.1

Amplify CLI Version

12.3.0

What operating system are you using?

Mac

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

No manual changes made

Describe the bug

Not sure if this is the correct place to create this issue. After signing up using a social provider for the second time when the account was deleted previously, several user attributes are missing. When you create an account for the second time the app is already known by the social provider. When revoking the app in the social provider and create the account again the attributes are set.

Expected behavior

User attributes are set after signing up again after the user has deleted their account.

Reproduction steps

  1. Signup using a social provider with the following mapped attributes
Screenshot 2023-11-26 at 17 32 46 2. Delete account 3. Sign in / signup again using the social provider 4. Missing the firstName and lastName attributes

Project Identifier

5675798e9d682c6bb49bd299ccfc6216

Log output

# Put your logs below this line


Additional information

No response

Before submitting, please confirm:

  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
  • I have removed any sensitive information from my code snippets and submission.
@steptro steptro added the pending-triage Issue is pending triage label Nov 26, 2023
@ykethan
Copy link
Member

ykethan commented Nov 27, 2023

Hey @steptro, thank you for reaching out. On diving deeper into the issue I was able to find that this is currently an expected behaviour when using Apple as social provider.
The behaviour is currently being tracked on aws-amplify/amplify-js#10182
The forum here linked in the last comment on the issue provides this information.

@ykethan ykethan added auth Issues tied to the auth category of the CLI pending-response Issue is pending response from the issue author labels Nov 27, 2023
@stephantromer-pon
Copy link

Hey @ykethan, thanks for responding so quickly! I will monitor the links you mentioned.

@josefaidt
Copy link
Contributor

Closing in favor of tracking existing item

@josefaidt josefaidt closed this as not planned Won't fix, can't repro, duplicate, stale Feb 2, 2024
Copy link

github-actions bot commented Feb 2, 2024

⚠️COMMENT VISIBILITY WARNING⚠️

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auth Issues tied to the auth category of the CLI pending-response Issue is pending response from the issue author pending-triage Issue is pending triage
Projects
None yet
Development

No branches or pull requests

4 participants