aws-amplify / amplify-cli

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

aws amplify cli becoming non-responsive #13847

Closed vikaskgahlawat closed 2 weeks ago

vikaskgahlawat commented 2 weeks ago

How did you install the Amplify CLI?

npm

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

v16.17.0

Amplify CLI Version

12.12.4

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 manual changes

Describe the bug

I have an amplify react application setup with two environments "vikas" and "developer". My application was on the env "vikas".

  1. When I run "amplify env checkout developer" it keeps waiting forever.
  2. I went through some blogs and people suggested that my local configuration might be corrupted. I removed the local configuration and all local environments were deleted.
  3. Tried to initiate the local amplify using the command "amplify pull --appId d2mb8lyicrgsqx --envName vikas" but this also keeps waiting after saying the backend environment was found. image

    this has been running for more than an hour.

Expected behavior

Amplify application in local should be instantiated properly. Switching between environments should work properly.

Reproduction steps

Not sure if this is amplify configuration issue of some virtual environment issue on my machine.

Project Identifier

No response

Log output

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

Additional information

No response

Before submitting, please confirm:

vikaskgahlawat commented 2 weeks ago

Looks like downloading the "#current-cloud-backend.zip" file is taking forever even though I have enough bandwidth.

image
vikaskgahlawat commented 2 weeks ago

It started to download on its own. Not sure what was the issue but its working now.

github-actions[bot] commented 2 weeks 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.