Skip to content
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

Build Timing out using latest Amplify CLI v12.12.6 and Amplify Studio Gen 1 #13903

Open
2 tasks done
kimberlyas opened this issue Aug 27, 2024 · 3 comments
Open
2 tasks done
Labels
hosting Issues tied to hosting category pending-response Issue is pending response from the issue author pending-triage Issue is pending triage platform-pull Issues related to `amplify pull`

Comments

@kimberlyas
Copy link

How did you install the Amplify CLI?

npm

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

16.13.0

Amplify CLI Version

12.12.6

What operating system are you using?

Ubuntu

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

I am unable to deploy my Amplify App using the latest Amplify CLI v12.12.6. I am working in a Gen 1 Amplify Project with Amplify Studio enabled. And I am deploying using the Amplify CI/CD pipeline and default build image (Amazon Linux 2023). The issue is that the build keeps timing out without any errors being shown even after setting the build timeout to its max at 2 hrs. So I am unable to deploy the app.

Build consistently times out at this point below:

2024-08-02T20:04:50.408Z [WARNING]: ✔ Successfully pulled backend environment staging from the cloud.
2024-08-02T20:04:50.488Z [INFO]: ✅
2024-08-02T20:04:52.219Z [INFO]: �[33mNote: It is recommended to run this command from the root of your app directory�

Expected behavior

The Amplify App should have completed its build and be deployed successfully using the latest Amplify CLI version.

Reproduction steps

  1. Create a Gen 1 Amplify project and enable Amplify Studio.
  2. Add Amplify resources - api & auth.
  3. Trigger CI pipeline build and deploy using latest CLI in build settings.

Project Identifier

No response

Log output

# Put your logs below this line


Additional information

In troubleshooting, I was able to deploy by downgrading the Amplify CLI in the build settings to a previous version v12.0.3 in order for the app to build and deploy successfully.

So it seems the issue is with the latest versions of the Amplify CLI where they don't build Gen 1 Amplify Studio projects.

Before submitting, please confirm:

  • 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.
@kimberlyas kimberlyas added the pending-triage Issue is pending triage label Aug 27, 2024
@ykethan
Copy link
Member

ykethan commented Aug 28, 2024

Hey @kimberlyas, thank you for reaching out. Could you provide us the app-id and region?
additionally, does this occurs locally as well? for example: when running a pull in a empty directory or the existing app
Are there any additional outputs on if you add AMPLIFY_ENABLE_DEBUG_OUTPUT to true as environment variable and run a build?

@ykethan ykethan added hosting Issues tied to hosting category pending-response Issue is pending response from the issue author platform-pull Issues related to `amplify pull` labels Aug 28, 2024
@kimberlyas
Copy link
Author

Hi @ykethan, please see requested information:

App ID: d3gljibf5lo8bp
Region: us-east-1

When pulling the app, I don't experience any errors. Upon enabling the variable given, I see some additional warning outputs below both locally and in the deploy build:

[WARNING] @aws-cdk/aws-apigatewayv2-alpha.WebSocketApiKeySelectionExpression is deprecated. This API will be removed in the next major release. [WARNING] @aws-cdk/aws-apigatewayv2-alpha.WebSocketApiKeySelectionExpression is deprecated. This API will be removed in the next major release. [WARNING] @aws-cdk/aws-apigatewayv2-alpha.MappingValue is deprecated. This API will be removed in the next major release.

Please see full deploy build output when using latest CLI version (v12.12.6) below:
BUILD.txt

@github-actions github-actions bot removed the pending-response Issue is pending response from the issue author label Sep 2, 2024
@ykethan
Copy link
Member

ykethan commented Sep 4, 2024

Hey @kimberlyas, thank you for the information. With the latest versions of Amplify you will need to update the CDK libraries and the extensibility package . Refer to migration documentation: https://docs.amplify.aws/gen1/react/tools/cli/migration/aws-cdk-migration/#how-do-i-migrate
On updating this, could you retry the build with the latest version of Amplify CLI and let us know if this mitigates the issue.

@ykethan ykethan added the pending-response Issue is pending response from the issue author label Sep 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hosting Issues tied to hosting category pending-response Issue is pending response from the issue author pending-triage Issue is pending triage platform-pull Issues related to `amplify pull`
Projects
None yet
Development

No branches or pull requests

2 participants