Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Command failed with exit code 1: /Users/atk/.amplify/lib/aws-amplify-amplify-frontend-ios/resources/amplify-xcode import-config --path=... #3501

Closed
2 tasks done
atkreis opened this issue Feb 6, 2024 · 4 comments
Labels
bug Something isn't working dev tools Issues related to developer tools transferred This issue was transferred from another Amplify project

Comments

@atkreis
Copy link

atkreis commented Feb 6, 2024

How did you install the Amplify CLI?

npm

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

v21.2.0

Amplify CLI Version

12.10.1

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

Describe the bug

Ran "amplify pull --appId d21e2vnesg1g3q --envName staging" on a project that should have already been synced ("amplify pull" kept giving me "--envName" not being defined) and received the error:

Updating Xcode project:
🚫 xcodeProject:
-- Caused by: notFound(path: "/Users/atk/Documents/Projects/GitHub/Harlie-Push/Harlie")
🛑 Command failed with exit code 1: /Users/atk/.amplify/lib/aws-amplify-amplify-frontend-ios/resources/amplify-xcode import-config --path=/Users/atk/Documents/Projects/GitHub/Harlie-Push/Harlie

Expected behavior

Expected it to just work

Reproduction steps

See above

Project Identifier

c09af5259c6aae63cf8a3fc2829bd105

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.
@atkreis atkreis added the pending-triage Issue is pending triage label Feb 6, 2024
@josefaidt
Copy link

Hey @atkreis 👋 thanks for raising this! I'm going to transfer this over to our swift repo for tracking 🙂

@josefaidt josefaidt transferred this issue from aws-amplify/amplify-cli Feb 7, 2024
@josefaidt josefaidt added the transferred This issue was transferred from another Amplify project label Feb 7, 2024
@lawmicha lawmicha added the dev tools Issues related to developer tools label Feb 9, 2024
@thisisabhash thisisabhash removed the pending-triage Issue is pending triage label Feb 9, 2024
@lawmicha
Copy link
Contributor

Hi @atkreis, it looks like maybe it's trying to modify the Xcode project but ran into an unexpected file structure. Are you able to see the amplifyconfiguration.json file still generated within the amplify folder ? A workaround would be to drag this configuration file over to the app target you want to consume the file from and make sure Add to target is checked off.

@lawmicha lawmicha added the bug Something isn't working label Feb 13, 2024
@harsh62
Copy link
Member

harsh62 commented Feb 23, 2024

Closing in favor of #3139

@harsh62 harsh62 closed this as completed Feb 23, 2024
Copy link
Contributor

⚠️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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working dev tools Issues related to developer tools transferred This issue was transferred from another Amplify project
Projects
None yet
Development

No branches or pull requests

5 participants