All Amplify CLI Commands Failing

[jordanemergeio]

How did you install the Amplify CLI?

npm

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

17.9.1

Amplify CLI Version

12.5.0

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 made

Describe the bug

Running any amplify cli command all of a sudden produces the following error:

File at path: '/Users/jordan/repos/aws-amplify/amplify-app/amplify/#current-cloud-backend/amplify-meta.json' does not exist

Expected behavior

The cli commands should execute

Reproduction steps

Run 'amplify status' in the root directory of my Angular AWS Amplify project.

Project Identifier

65d6f99ec89e8ef23025ce5b0aeba58c

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.

[NoellaMarie501]

I have a similar problem. I used both Linux/Ubuntu and Windows. after installing amplify cli with "npm install -g @aws-amplify/cli" still unable to use any amplify command

[ykethan]

Hey @jordanemergeio, thank you for reaching out. The issue appears to be similar to #12766.
Could you upgrade the Amplify CLI version, then try pulling the backend using the pull command amplify pull --appId <app-id> --envName <env-name> --debug with the debug in an empty directory outside your existing application directory? Does this also throw the same error?

If the pull does throw the same error; Could you check the AWS S3 console for the deployment bucket, the name should be similar to amplify-<app-name>-<env-name>-34648-deployment.
Download and open the #current-cloud-backend.zip, verify if the amplify-meta.json does exist?

@NoellaMarie501 could you open a new GitHub issue with information on the behaviours you are experiencing.

[richie1720]

I think I am having the same issue. None of the amplify commands are working (see issue here)

[thecloudslayer]

I was having the same issue. If I run sudo in front, it works. sudo amplify status @jordanemergeio

[josefaidt]

Hey @richie1720 , @thecloudslayer 👋 was the CLI installed with sudo? or does the npm package live outside your HOME directory (i.e. is the absolute path of which amplify outside of your user's HOME directory)?

[josefaidt]

Closing due to inactivity

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

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.
If you wish to keep having a conversation with other community members under this issue feel free to do so.