Closed cDask closed 3 years ago
I ran with the same issue today just by following the instructions on the tutorial. My setup: macOS Mojave 10.14.6 node --version v10.6.0 npm --version 6.1.0 git --version 2.20.1 (Apple Git-117)
amplify push ⠋ Fetching updates to backend environment: dev from the cloud.(node:4925) ExperimentalWarning: The fs.promises API is experimental ✖ There was an error pulling the backend environment dev. An error occurred during the push operation: EEXIST: file already exists, mkdir '/Users/gregoriomarquez/dagtus/oasis/aws/amplify/vue/projects/gettingStartedApp/myamplifyproject/amplify/.temp/#current-cloud-backend'
I tried the fix mentioned by @cDask but have'nt had success.
I had an existing project using older Amplify libraries. Everything was building and working correctly. Then, I updated my PodFile to new libraries (1.0.0), built my code, but then I was no longer able to issue an amplify pull
or amplify push
thereafter. Furthermore, amplify status
now claims that all of my resources are in the Create state, even though I haven't changed any of them. I did, however, run an amplify init
after updating my pods. I don't know how to get my project back to a working state.
Error: EEXIST: file already exists, mkdir '/Users/zpodolyak/Projects/<myapp>/amplify/.temp/#current-cloud-backend'
I've been having this issue for a long time and can't find a fix. I cannot checkout any amplify environment.
$ amplify env checkout sandbox
✖ There was an error initializing your environment.
EEXIST: file already exists, symlink '..\acorn\bin\acorn' -> '/home/ec2-user/environment/application-root/amplify/.temp/#current-cloud-backend/function/graphqlfunctions/lib/nodejs/node_modules/.bin/acorn'
This happened when I switched from my Windows desktop to AWS Cloud9
This is a duplicate of https://github.com/aws-amplify/amplify-cli/issues/2948 Currently the CLI can not handle symlinks in Lambda functions due to the zip and unzip operations of the #current-cloud-backend folder. please reference the comment on how to unblock your project.
@GregorioMarquez @zpodolyak Did you guys have symlinks in your project? if not, then they are different issues, you can remove the .temp folder and that should unblock you, if you are still blocked, please open another github issue so we can address them separately.
closing as issue seems to be caused by symlinks in the lambda zip folder. Please open a new issue if you believe there is something else at play.
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.
Looking for a help forum? We recommend joining the Amplify Community Discord server *-help
channels for those types of questions.
Describe the bug Getting the following bug when running amplify pull, push and publish
Have tried to delete the function in question using amplify remove function which seems to have succeeded as it is no longer listed when running amplify remove function again. As well as it not being listed when running amplify status.
Have also tried deleting the .temp folder and running amplify pull again which gave me a new error:
Then running amplify status after this gives me:
Which Im only able to fix by deleting everything in the #current-cloud-backend folder and copying these folders from my backend folder which was suggested to me by AWS support.
Amplify CLI Version 4.29.3
Terminal Error
Expected behavior The amplify pull,push and publish to go through.
Desktop (please complete the following information):