Deployments failing with no error message

[amirhajimirsadeghi]

Before opening, please confirm:

• I have checked to see if my question is addressed in the FAQ.
• 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.

Describe the bug

This is the only message I see in my deployment step:

2021-04-28T23:05:35 [INFO]: Starting Deployment
2021-04-28T23:05:35 [ERROR]: Failed to deploy

This is happening for my qa and prod environments. I tried disconnecting the branch and reconnecting, deploying old version, redploying. It just keeps getting to the deployment stage and not giving me any info. Just failinh

Expected behavior

To either deploy the app successfully or give a more descriptive message

Reproduction steps

1. Go to my amplify application
2. Click redeploy this version

Build Settings

version: 0.1
backend:
  phases:
    build:
      commands:
        - '# Execute Amplify CLI with the helper script'
        - amplifyPush --simple
frontend:
  phases:
    preBuild:
      commands:
        - yarn install
    build:
      commands:
        - yarn run build:$USER_BRANCH
  artifacts:
    baseDirectory: build
    files:
      - '**/*'

Additional information

No response

[github-actions]

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.

[ac3charland]

Was experiencing this same issue and was able to find a fix. I discovered I was using the latest version Amplify CLI in my build settings, which must have recently introduced a breaking change.

To fix:

In the Amplify console, go to Build settings > Build image settings > Edit
Specify the version of Amplify CLI that's in your project's package.json (e.g. 4.29.4)

Source: #1298 (comment)

[amirhajimirsadeghi]

Thanks, @ac3charland I put it to 4.49.0 and that did it for me! I wonder if this is an issue with CLI version 4.50.0