amplify-cli: Amplify pull stuck on fetching updates (latest CLI version)

Describe the bug When running amplify pull on the latest CLI version, the console stays stuck on:

⠏ Fetching updates to backend environment: dev from the cloud.

Rolling back to 4.23.0 fixes the issue.

Amplify CLI Version 4.23.1

About this issue

Original URL
State: closed
Created 4 years ago
Reactions: 8
Comments: 20 (5 by maintainers)

Commits related to this issue

fix(cli): moving the spinner above category initialization tasks stopping the spinner before running category init tasks since the spinner can swallow outputs (such as questions via inquirer) re #47... — committed to SwaySway/amplify-cli by SwaySway 4 years ago
fix(cli): moving the spinner above category initialization tasks (#4836) * fix(cli): moving the spinner above category initialization tasks stopping the spinner before running category init tasks ... — committed to aws-amplify/amplify-cli by SwaySway 4 years ago
fix(cli): moving the spinner above category initialization tasks (#4836) * fix(cli): moving the spinner above category initialization tasks stopping the spinner before running category init tasks ... — committed to nikhname/amplify-cli by SwaySway 4 years ago
fix(cli): moving the spinner above category initialization tasks (#4836) * fix(cli): moving the spinner above category initialization tasks stopping the spinner before running category init tasks ... — committed to MLH-Fellowship/amplify-cli by SwaySway 4 years ago
fix(cli): moving the spinner above category initialization tasks (#4836) * fix(cli): moving the spinner above category initialization tasks stopping the spinner before running category init tasks ... — committed to MLH-Fellowship/amplify-cli by SwaySway 4 years ago

Most upvoted comments

Just for anyone else on this issue. It was still happening for me with amplify 4.32.0. I worked out eventually it was the version of node I had… upgraded from 14.0.0 to 14.2.0 and amplify works again using 4.32.0.

paulnolan7 on Nov 6, 2020

@aavargasp I was able to reproduce this - Working on a fix

SwaySway on Jul 15, 2020

Just for anyone else on this issue. It was still happening for me with amplify 4.32.0. I worked out eventually it was the version of node I had… upgraded from 14.0.0 to 14.2.0 and amplify works again using 4.32.0.

Oddly enough, I did the same (v14 -> v15.5) and it successfully pulled from the cloud. Not quite sure what’s changed that upgrading node worked. Also possible it was coincidence.

I had the same issue and can confirm that shifting from 14.0.0 to 15.0.0 did the trick

eddie-atkinson on Feb 19, 2021

I had exact the same issue, rolled cli back to 4.16.1 and it works again.

@pragyajha updating the amplify-cli to the latest version may help, I know they have added some related patches and some activity log messages.

@hugozap I updated version to 4.29.3, but still no luck:(

ripley on Oct 8, 2020

Just for anyone else on this issue. It was still happening for me with amplify 4.32.0. I worked out eventually it was the version of node I had… upgraded from 14.0.0 to 14.2.0 and amplify works again using 4.32.0.

Oddly enough, I did the same (v14 -> v15.5) and it successfully pulled from the cloud. Not quite sure what’s changed that upgrading node worked. Also possible it was coincidence.

kevcam4891 on Dec 28, 2020

Closing this issue as the fix for this has been merged and is included in v4.24.2. Should you experience this again after v4.24.2 please comment below.

SwaySway on Jul 17, 2020

I updated nodeJS and deleted amplify folder.

pooya1361 on Nov 14, 2020