amplify-js: Login with google for the second time : email Attribute cannot be updated

It seems after two years of my report, you guys still don’t fix it @sammartinez Actually, I moved away from Cognito a long time ago and can’t test it anymore. It was a horrible experience with a lot of bugs and a lack of necessary features

Hi @anjanvb - can you please create a new Github issue with the details we need to troubleshoot this?

Still have this issue. Terrible. User pool is already in production. Can’t recreate it…

I can reproduce the same issue. email is not mandatory for my pool, and is selected as readable and writable by my app client. First time login succeeds (and the email attribute on my Cognito user is populated), subsequent logins fail with ‘user+attributes%3A+email%3A+Attribute+cannot+be+updated’ error.

I worked around it by creating a custom attribute called ‘emailaddress’ and mapped the Google email attribute to that.

@anjanvb Thanks for the follow up and clarification, I’m glad you were able to resolve this.

I believe the confusion comes from the use of the terms "writable" and "mutable". Note that these are different and independent, in the way that "mutable" is specific to the userPool and "writable" is specific to the userPoolClient.

A scenario to help elaborate on this:

1. You have the attribute set to "immutable" on the userPool - meaning once it is set, it cannot be changed
2. Have the same attribute set to "writable" on the userPoolClient - meaning the userPoolClient can write to the userPool attribute.
3. Login the first time, and the userPoolClient writes to the userPool attribute, setting the value.
4. Login a second time, and the userPoolClient fails to write to the userPool attribute as it is "immutable" and cannot be changed.

This will result in a situation similar to what you and others have faced on this issue.

In short, be sure you are setting the attribute to both "mutable" on the userPool config and "writable" on the userPoolClient config.

References

• UserPool Mutable definition
• UserPoolClient Writable definition
• Mapping Attributes To Identity Provider

Hi @uchar - can you please submit a new Github issue for us following our template so that we can investigate this? https://github.com/aws-amplify/amplify-js/issues/new?assignees=&labels=&template=1.bug_report.yaml

@uchar I tried to reproduce issue but couldn’t. I have the email attribute as required in my user pool setting. Is your email attributes mutable? There is a Set attribute read and write permissions secton under App clients.

@uchar Hi, did you map the email attributes from google to the Cognito User Pool? There is an section Attribute mapping under Federation in the Cognito User Pool console that you can do the mapping.

Yes I did, and It works fine for the first time but trying to sign in for the second time give me that error

@uchar Hi, did you map the email attributes from google to the Cognito User Pool? There is an section Attribute mapping under Federation in the Cognito User Pool console that you can do the mapping.