amplify-cli: Deployments Failing to Build: Skipping override due to SyntaxError
Before opening, please confirm:
- I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
- I have searched for duplicate or closed issues.
- I have read the guide for submitting bug reports.
- 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.
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v14.18.1
Amplify CLI Version
7.6.15
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
Amplify Categories
Not applicable
Amplify Commands
push
Describe the bug
Locally we are able to build and push our enviornment changes. But the CI/CD pipeline is resulting in the following error:
# Starting phase: build
2022-02-09T00:01:45.918Z [INFO]: [0mAmplify AppID found: dx3sjbu3eyh20. Amplify App name is: productwind[0m
2022-02-09T00:01:46.008Z [INFO]: [0mBackend environment master found in Amplify Console app: productwind[0m
2022-02-09T00:01:48.234Z [WARNING]: - Fetching updates to backend environment: master from the cloud.
2022-02-09T00:01:50.677Z [WARNING]: - Building resource auth/userPoolGroups
2022-02-09T00:01:50.679Z [WARNING]: - Building resource auth/productwind
2022-02-09T00:01:50.818Z [WARNING]: - Building resource api/productwind
2022-02-09T00:01:50.819Z [WARNING]: - Building resource storage/productwind
2022-02-09T00:01:59.354Z [INFO]: 🛑 Error: Skipping override due to SyntaxError: Unexpected token (2:13)
2022-02-09T00:01:59.358Z [WARNING]: 2022-02-09T00:01:59.357Z - error: uncaughtException: Skipping override due to SyntaxError: Unexpected token (2:13)
date=Wed Feb 09 2022 00:01:59 GMT+0000 (Coordinated Universal Time), pid=1885, uid=0, gid=0, cwd=/codebuild/output/src554682081/src/productwind-web, execPath=/root/.nvm/versions/node/v14.18.1/bin/node, version=v14.18.1, argv=[/root/.nvm/versions/node/v14.18.1/bin/node, /root/.nvm/versions/node/v14.18.1/bin/amplify, pull, --amplify, {"envName":"master","appId":"dx3sjbu3eyh20"}, --providers, {"awscloudformation":{"configLevel":"project","useProfile":true,"profileName":"default"}}, --no-override, --no-codegen, --yes], rss=655273984, heapTotal=539148288, heapUsed=469028376, external=4338755, arrayBuffers=2077113, loadavg=[2.38, 1.64, 0.73], uptime=395.01, trace=[], stack=undefined
2022-02-09T00:01:59.390Z [ERROR]: !!! Build failed
2022-02-09T00:01:59.390Z [ERROR]: !!! Non-Zero Exit Code detected
2022-02-09T00:01:59.390Z [INFO]: # Starting environment caching...
2022-02-09T00:01:59.391Z [INFO]: # Uploading environment cache artifact...
2022-02-09T00:01:59.451Z [INFO]: # Environment caching completed
Terminating logging...
Our deployment pipelines are now blocked because of this.
We tried reverting the latest changes and building with other versions, but still no luck
I was able to checkout the environment that was failing and build/deploy locally just fine so it seems like there is some sort of issue on the CI/CD Amplify hosting.
Expected behavior
Build and deploy without error
Reproduction steps
Deploy on Amplify CI/CD web service.
App ID: dx3sjbu3eyh20 Environment: master and production
GraphQL schema(s)
# Put schemas below this line
Log output
# Put your logs below this line
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 3
- Comments: 27 (6 by maintainers)
Our CI/CD-Pipeline failed too without changing anything. We have to merge some updates to production, but this issue blocked our workflow. We are currently using also the workaround for storage overrides with the amplify-meta as mentioned by @aqarcoSys. This issue is high priority. We fixed the amplify to a specific ( for us stable ) version to prevent this kind of issues, but as we see, this doesn’t helped…