I have just ran amplify upgrade and now amplify doesn't work at all

rafaelfaria commented 2 years ago

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?

npm install -g @aws-amplify/cli

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

v16.16.0

Amplify CLI Version

can't see anymore

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

Amplify Categories

Not applicable

Amplify Commands

push

Describe the bug

After installing the latest upgrade, my amplify doesn't work anymore.

$ node -v
v16.16.0
➜  Sites/raf/myapp  git:(master)
$ amplify -v
➜  Sites/raf/myapp  git:(master)
$ amplify push --forcePush --yes
➜  Sites/raf/myapp  git:(master)
$ amplify status
➜  Sites/raf/myapp  git:(master)

It just goes to the next line. Nothing happens at all.

Expected behavior

To work? :P

Reproduction steps

I got a warning saying that there was a new version for amplify.
I ran amplify upgrade. It asked me for root.
so I ran sudo amplify upgrade
It finished installing
When I try amplify status or amplify push nothing happens

GraphQL schema(s)

```graphql # Put schemas below this line ```

Project Identifier

No response

Log output

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

Additional information

No response

josefaidt commented 2 years ago

Hey @rafaelfaria :wave: thanks for raising this! To better understand the context of the issue I have a few follow-up questions:

I ran amplify upgrade. It asked me for root.

What did the messaging say when it prompted for root? Was the CLI or npm installed with sudo?

Is the CLI hanging and you are exiting the flow with ctrl+c before it responds, or is it simply not responding and returning the new line?

What version are you upgrading from?

josefaidt commented 2 years ago

Closing due to inactivity

krishnu9 commented 2 years ago

Hi @josefaidt , I'm facing the same issue. None of the amplify commands run after the upgrade. It just returns a blank new line (doesn't hang or anything). The error messaging said this pkrishnu@147ddada7eb4 mapfundingcalculator % amplify upgrade Downloading latest Amplify CLI 0% [ ] 0.0 seconds left🛑 EACCES: permission denied, open '/Users/pkrishnu/.amplify/bin/amplify-pkg-macos' Error: EACCES: permission denied, open '/Users/pkrishnu/.amplify/bin/amplify-pkg-macos' pkrishnu@147ddada7eb4 mapfundingcalculator % sudo amplify upgrade Password: Downloading latest Amplify CLI 100% [========================================] 0.0 seconds left Successfully upgraded to Amplify CLI version 10.4.1!

jackmandelkorn commented 1 year ago

Facing the same issue here after running sudo amplify upgrade

LachlanKI commented 1 year ago

Facing the same issue here after running sudo amplify upgrade

Same! :/

AkshathaLaxmi commented 1 year ago

same issue

chrsle commented 11 months ago

same issue

exai-sukh commented 11 months ago

same issue

josefaidt commented 11 months ago

Hey folks :wave: please open a new bug report if you are experiencing this issue

thecloudslayer commented 10 months ago

same issue!

chrsle commented 10 months ago

this can be solved with sudo chown -R $(whoami):$(id -gn) ~/.amplify

aws-amplify / amplify-cli