can't init / pull an existing project

[davidgamify]

Before opening, please confirm:

• I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
• I have searched for duplicate or closed issues.
• I have read the guide for submitting bug reports.
• 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.

How did you install the Amplify CLI?

npm

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

v14.16.0

Amplify CLI Version

9.1.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

Amplify Categories

auth, storage, function, api, analytics

Amplify Commands

init, pull

Describe the bug

When we do either an amplify init (with an existing project) or an amplify pull on a new machine (or VM), we receive the following error:
Could not initialize 'staging': ENOENT: no such file or directory, stat '/aws/mde/work/lyferize/amplify/.temp/#current-cloud-backend/function/lyferizeUtils/lib/python/venv/bin/python'

Expected behavior

The command should prompt us whether we want to update the backend and then allow us to develop using the framework.

Reproduction steps

1. amplify init --appId dcjj80gy8efkc
   Note: It is recommended to run this command from the root of your app directory
   ? Do you want to use an existing environment? Yes
   ? Choose the environment you would like to use: staging
   Using default provider awscloudformation
   ⠧ Initializing your environment: staging🛑 Could not initialize 'staging': EEXIST: file already exists, symlink '../../../../../../../../../../../.pyenv/versions/3.8.8/bin/python' -> '/aws/mde/work/lyferize/amplify/.temp/#current-cloud-backend/function/lyferizeUtils/lib/python/venv/bin/python'

GraphQL schema(s)

# Put schemas below this line

Project Identifier

/var/folders/c2/5229qw4n3593qffh12m5xs_c0000gn/T/lyferize/report-1657577723600.zip

Log output

# Put your logs below this line

Additional information

This is a critical issue as we can only deploy our product from exactly one laptop. If something happens to this laptop, we cannot deliver any updates/fixes to our product.

[josefaidt]

Hey @davidgamify 👋 thanks for raising this! To better understand the context of the issue and provide a suitable workaround may I ask for the steps needed to reproduce this issue? Can you try following the steps of this gist to manually remove the symlink from your #current-cloud-backend archive? https://gist.github.com/josefaidt/be56f2a8a821b084b66e40ce51e20b44

[davidgamify]

I followed the instructions in the linked post. Now, I cannot even access the staging env in the console or from the cli.

…

On Tue, Jul 12, 2022 at 7:20 AM josef ***@***.***> wrote: Hey @davidgamify <https://github.com/davidgamify> 👋 thanks for raising this! To better understand the context of the issue and provide a suitable workaround may I ask for the steps needed to reproduce this issue? Can you try following the steps of this gist to manually remove the symlink from your #current-cloud-backend archive? https://gist.github.com/josefaidt/be56f2a8a821b084b66e40ce51e20b44 — Reply to this email directly, view it on GitHub <#10740 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2AO5IHVPODZEJ7ECRFV5D3VTVWKPANCNFSM53I7X4AA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

--

[josefaidt]

This issue seems similar to #10138 (comment), which was previously closed. What are the steps you followed prior to receiving this issue?

[davidgamify]

We resolved the issue by removing the symlinks from the .zip file and re-uploading it to s3.

…

On Thu, Jul 14, 2022 at 1:48 PM josef ***@***.***> wrote: This issue seems similar to #10138 (comment) <#10138 (comment)>, which was previously closed. What are the steps you followed prior to receiving this issue? — Reply to this email directly, view it on GitHub <#10740 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2AO5ICO54QNATNK5BIRH4DVUBVJ3ANCNFSM53I7X4AA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

--

[ykethan]

Glad to hear that you were able to mitigate the issue. Please feel free in reaching out to us again if you are observing any behaviors.