#current-cloud-backend.zip and amplify-meta.json file not found after successful amplify pull about amplify-cli HOT 7 OPEN

Hey @nbtrieu, from the information provided, this issue appears to be similar to #13335. was the project previously or currently being pulled into a folder that sync with cloud storage like iCloud or OneDrive?
Could you download the #current-cloud-backend.zip archive from the S3 deployment bucket on the console(the bucket name ends with -deployment and contains the name of the project) and check if the artifact contains any duplicate files?

from amplify-cli.

Hello @ykethan, thank you for your response! The project is being pulled into a folder that syncs with iCloud (although upload is still pending); should I disable syncing?
I have also downloaded the #current-cloud-backend.zip archive from the S3 deployment bucket and checked that it contains duplicate cli.json files (cli.json, cli 2.json, cli 3.json). Could this be related to the missing amplify-meta.json file in any way?

from amplify-cli.

Hey @nbtrieu, before making any changes do you observe the amplify-meta.json in the #current-cloud-backend.zip?
if file is present, you can download the #current-cloud-backend.zip archive, unzip, carefully remove duplicate files, re-zip, and re-upload. do ensure when re-zipping the folder this does not created a nested folder in the zip.
then in new directory outside the existing project directory run amplify pull --appId <app-id> --envName <env-name> to check for a successful pull.

from amplify-cli.

Wait sorry so by "new directory outside the existing project directory" do you mean a new and empty directory?
Also when the modified #current-cloud-backend.zip is re-uploaded, will the previous archive be automatically overwritten?

from amplify-cli.

@nbtrieu yes, for testing purposes create a new directory outside the existing path that may not be connected to a cloud backup service such as iCloud/OneDrive.
I would recommend keeping a copy of the #current-cloud-backend.zip locally before re-uploading the new version of #current-cloud-backend.zip containing the removed duplicated files. The re-upload should override the existing zip or you can deleted it in the s3 bucket and upload the new zip.

from amplify-cli.

Thank you for the clarification, I did as you said but now I cannot pull the backend at all...

from amplify-cli.

@nbtrieu can add the --debug and rerun the pull.
how the does the new zip structure look like, do ensure when re-zipping the folder this does not created a nested #current-cloud-backend folder in the zip. this commonly happens when we try to right click the folder and zip it.
on the terminal you can also do

cd #current-cloud-backend/
zip -r "../#current-cloud-backend.zip" *

from amplify-cli.