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

aws amplify cli becoming non-responsive #13847

Closed
2 tasks done
vikaskgahlawat opened this issue Jul 9, 2024 · 3 comments
Closed
2 tasks done

aws amplify cli becoming non-responsive #13847

vikaskgahlawat opened this issue Jul 9, 2024 · 3 comments
Labels
pending-triage Issue is pending triage

Comments

@vikaskgahlawat
Copy link

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:

  • 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.
@vikaskgahlawat vikaskgahlawat added the pending-triage Issue is pending triage label Jul 9, 2024
@vikaskgahlawat
Copy link
Author

vikaskgahlawat commented Jul 9, 2024

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

@vikaskgahlawat
Copy link
Author

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

Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending-triage Issue is pending triage
Projects
None yet
Development

No branches or pull requests

1 participant