amplify-cli: Unable to push any new changes

Describe the bug Unable to push any new changes in amplify . It show’s an error of Existing schema attributes cannot be modified or deleted.

Amplify CLI Version 4.44.0

To Reproduce Try to update auth and add a new user pool group For detailed steps https://youtu.be/IhXZ-Ekex1Y

Error messages

UPDATE_FAILED      UserPool AWS::Cognito::UserPool Tue Feb 23 2021 00:55:49 GMT+0530 (India Standard Time) Existing schema attributes cannot be modified or deleted. (Service: AWSCognitoIdentityProvider; Status Code: 400; Error Code: InvalidParameterException; Request ID: null; Proxy: null)

UPDATE_FAILED authchedarAuthTest AWS::CloudFormation::Stack Tue Feb 23 2021 00:55:52 GMT+0530 (India Standard Time) Embedded stack arn:aws:cloudformation:eu-west-2:251651594881:stack/amplify-chedarv2-staging-232034-authchedarAuthTest-14GAGGNY7CAL5/ed59d3a0-49fe-11eb-bd5a-023389416292 was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: The following resource(s) failed to update: [UserPool]. 

✖ An error occurred when pushing the resources to the cloud

Resource is not in the state stackUpdateComplete
An error occurred during the push operation: Resource is not in the state stackUpdateComplete

Expected behavior A clear and concise description of what you expected to happen.

Screenshots

Desktop

OS: Ubuntu in WSL2
Node Version - 12.18.4

About this issue

Original URL
State: closed
Created 3 years ago
Reactions: 1
Comments: 29 (12 by maintainers)

Most upvoted comments

@akshbhu The attribute is showing up in cognito

My amplify logs of last 3 days when the problem started happening

amplify-cli-2021-02-24.log amplify-cli-2021-02-22.log amplify-cli-2021-02-23.log

I have also mailed you the amplify folder it will be from email id dev@chedar.fr

DevTGhosh on Feb 25, 2021

I was trying to find better solutions and just came across this where a user updated the amplify-cfn-templates/auth with the correct auth-cloudformation-template.yml file via S3 user interface and then he could run amplify push properly.

sharmaadityaHQ on Feb 23, 2021

I also faced the Resource is not in the state stackUpdateComplete while doing amplify push in a sample project where I followed the steps you mentioned but I was able to fix this by creating a new project and running amplify configure and amplify init again. Here is a reference of a similar issue - https://github.com/aws-amplify/amplify-cli/issues/82. Can you try after running amplify configure again?

sharmaadityaHQ on Feb 22, 2021