Getting userpool error with no changes to userpool (only graphql api)

[isaac-rosterlab]

Before opening, please confirm:

• [X] I have checked to see if my question is addressed in the FAQ.
• [X] I have searched for duplicate or closed issues.
• [X] I have read the guide for submitting bug reports.
• [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id

dnbf8aqkmb1um

Region

ap-southeast-2

Amplify Console feature

Backend builds

Describe the bug

I have not made any changes to my userpool at all. I slightly changed the graphql API, then rebuilt and got this error. Then I tried rebuilding a previous build which was successful and it gave me the same error.

2022-01-14T02:57:10.369Z [INFO]: UPDATE_FAILED UserPool AWS::Cognito::UserPool Fri Jan 14 2022 02:57:06 GMT+0000 (Coordinated Universal Time) Invalid AttributeDataType input, consider using the provided AttributeDataType enum. (Service: AWSCognitoIdentityProviderService; Status Code: 400; Error Code: InvalidParameterException; Request ID:_________________; Proxy: null)

Expected behavior

I think the build should be successful when building previously successful builds. I think when only changing my API, I should not receive a user pool error.

Reproduction steps

Since I'm not effectively changing the backend at all, I only know how I produced it.

1. run build 160 which was previously successful
2. it fails

Build Settings

I'm using the default build image.

backend:
  phases:
    build:
      commands:
        - update-alternatives --install /usr/bin/python3 python3 /usr/local/bin/python3.8 11
        - /usr/local/bin/pip3.8 install --user pipenv
        - amplifyPush --simple

Additional information

No response

[github-actions[bot]]

Hi :wave:, thanks for opening! While we look into this...

If this issue is related to custom domains, be sure to check the custom domains troubleshooting guide to see if that helps. Also, there is a more general troubleshooting FAQ that may be helpful for other questions.

Lastly, please make sure you've specified the App ID and Region in the issue!

[batelhi]

Hello, Im having the same issue:

2022-01-22T17:22:05.098Z [INFO]: Following resources failed Resource Name: *** (AWS::Cognito::UserPool) Event Type: update Reason: Updates are not allowed for property - UsernameConfiguration. (Service: AWSCognitoIdentityProvider; Status Code: 400; Error Code: InvalidParameterException; Request ID: null; Proxy: null) 2022-01-22T17:22:05.100Z [WARNING]: ✖ An error occurred when pushing the resources to the cloud ✖ There was an error initializing your environment.

But I changed only the schema.graphql file. After failing I also rolled back my changes in the schema file but it still failing.

[ghost]

Hi @isaac-rosterlab and @batelhi 👋🏽, apologies for the delay. We are working on reproducing this and will provide an update once we have more information.

[SantoshRaoMea]

Hello, Im having the same issue:

2022 15:22:07 GMT+0000 (Coordinated Universal Time) Invalid AttributeDataType input, consider using the provided AttributeDataType enum. (Service: AWSCognitoIdentityProviderService; Status Code: 400; Error Code: InvalidParameterException; Request ID: 7682f3b7-b042-498c-b35b-e2c9848b51c5; Proxy: null) UPDATE_ROLLBACK_IN_PROGRESS - AWS::CloudFormation::Stack Mon Feb 07 2022 15:22:08 GMT+0000 (Coordinated Universal Time) The following resource(s) failed to update: [UserPool]. 2022-02-07T15:22:19.332Z [INFO]: 2022-02-07T15:22:19.333Z [INFO]: UPDATE_FAILED AWS::CloudFormation::Stack Mon Feb 07 2022 15:22:18 GMT+0000 (Coordinated Universal Time) Embedded stack arn:aws:cloudformation:eu-west-1::stack/amplify-*** was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: The following resource(s) failed to update: [UserPool].

[isaac-rosterlab]

@hloriana Any updates? I'm still getting the same issue

[CoachBenedetto]

Getting the same issue ...

Any of you found a working fix?