-
Notifications
You must be signed in to change notification settings - Fork 116
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
AWS Amplify CI/CD fail build backend by amplifyPush #1973
Comments
Hi 👋, 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 |
Hi @Athena96 unfortunately your solution did not work for me. I still get "AlreadyExistsException: Stack *** already exists" from amplifyPush |
@Rednoll can you update your buildspec to just use |
@swaminator I got another error: "auth headless is missing the following inputParams"
Previously it error can be fixed by |
@Rednoll after updating your backend statement to simply being |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Before opening, please confirm:
How did you install the Amplify CLI?
AWS Amplify CI/CD
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
5.0.0
What operating system are you using?
Linux (AWS Amplify CI/CD)
Amplify Categories
Not applicable
Amplify Commands
push
Describe the bug
When project try to build (after commit to branch or manually run build) it fails on build backend step with script:
App Id: d2205ysrekymt7
Region: us-east-2
It began happening after 09.06.2021 (it's date of last successful build of all my projects)
Maybe it can be related with aws-amplify/amplify-studio#57
Expected behavior
Standard obtaining aws-exports.js and CI/CD flow: Provision -> Build -> Deploy -> Verify
Reproduction steps
GraphQL schema(s)
No response
Log output
Additional information
No response
The text was updated successfully, but these errors were encountered: