You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If applicable, what version of Node.js are you using?
v20.10.0
Amplify CLI Version
12.10.0
What operating system are you using?
macOS 14.3.1
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No.
Describe the bug
I'm getting amplify/#current-cloud-backend/amplify-meta.json' does not exist error from amplify init and amplify pull.
And there is a nested #current-cloud-backend
$ ls amplify/\#current-cloud-backend/\#current-cloud-backend
amplify-meta.json awscloudformation functiontsconfig.json
api backend-config.json package.json
auth cli.json
Hey @yusukegoto, thank you for reaching out. Could you download the #current-cloud-backend.zip from the S3 deployment bucket on the AWS console. The bucket name should end with deployment and contain the app name.
if you do observe a nested current-cloud-backend in the zip, we could try carefully re-zipping the contents without creating a nested folder similar to as follows, then upload the zip and try pulling the env in a new empty folder outside your existing project directory to test.
cd /#current-cloud-backend/
zip -r "../#current-cloud-backend.zip" *
I've resolved this issue in a different way. I moved all files under a child #current-cloud-backend onto a parent #current-cloud-backend and running amplify push --force worked 🤷♂️
Then I can't try your suggested way. I'll try next if I have this again.
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.
How did you install the Amplify CLI?
asdf
If applicable, what version of Node.js are you using?
v20.10.0
Amplify CLI Version
12.10.0
What operating system are you using?
macOS 14.3.1
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No.
Describe the bug
I'm getting
amplify/#current-cloud-backend/amplify-meta.json' does not exist
error fromamplify init
andamplify pull
.And there is a nested
#current-cloud-backend
Expected behavior
amplify init
andamplify pull
run successfully.Reproduction steps
Project Identifier
Project Identifier: eeac7938f8313a01fd2c8550bffa6759
report-1709716696135.zip
Log output
Additional information
No response
Before submitting, please confirm:
The text was updated successfully, but these errors were encountered: