search

aws-amplify / amplify-cli

The AWS Amplify CLI is a toolchain for simplifying serverless web and mobile development.
Apache License 2.0
2.83k stars 823 forks source link

Amplify deployment failed #13820

Closed mysklc closed 4 months ago

mysklc commented 5 months ago

How did you install the Amplify CLI?

npm

If applicable, what version of Node.js are you using?

No response

Amplify CLI Version

12.10.0

What operating system are you using?

Windows 11

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

No Manual changes made.

Describe the bug

Deployment job timed out.

√ Zipping artifacts completed. | Deploying build artifacts to the Amplify Console..Job Timeout before succeeded × Deployment failed! Please report an issue on the Amplify Console GitHub issue tracker at https://github.com/aws-amplify/amplify-console/issues. 🛑 Job Timeout before succeeded

Resolution: Please report this issue at https://github.com/aws-amplify/amplify-cli/issues and include the project identifier from: 'amplify diagnose --send-report' Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

Session Identifier: 74799a23-8921-47a0-8744-0df996e4aa30 Project Identifier: 5ad9f6befc532dcb4ac971f083bb35f6

Expected behavior

Amplify successfully Published!

Reproduction steps

Executed the below commands in CLI

Project Identifier

Project Identifier: 5ad9f6befc532dcb4ac971f083bb35f6

Log output

``` # Put your logs below this line ```

Additional information

No response

Before submitting, please confirm:

ykethan commented 5 months ago

Hey @mysklc, Does this occur when retrying the publish command? Could you add the --debug to the publish command and provide us the output? Could you let us know the size of the build/dist folders?

ykethan commented 4 months ago

Closing the issue due to inactivity. Do reach out to us if you are still experiencing this issue

github-actions[bot] commented 4 months ago

This issue is now closed. Comments on closed issues are hard for our team to see. If you need more assistance, please open a new issue that references this one.