-
Notifications
You must be signed in to change notification settings - Fork 825
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
Command failed with exit code 1: in a ios project #13064
Comments
I am seeing the same behavior with both the npm-installed amplify cli (12.4.0 and 12.2.3) and the script-installed amplify cli from #13104 (comment). I am attempting to init a new xcode/ios project. Xcode 14.3.1 is installed. $ amplify pull --appId <app id> --envName staging
Opening link: https://us-east-1.admin.amplifyapp.com/admin/<app id>/staging/verify/?loginVersion=1
⠏ Confirm login in the browser or manually paste in your CLI login key:
Successfully received Amplify Studio tokens.
Amplify AppID found: <app id>. Amplify App name is: Hush
Backend environment staging found in Amplify Console app: Hush
? Choose your default editor: Xcode (macOS only)
✔ Choose the type of app that you're building · ios
? Do you plan on modifying this backend? Yes
✔ Successfully pulled backend environment staging from the cloud.
✅
✅ Successfully pulled backend environment staging from the cloud.
Run 'amplify pull' to sync future upstream changes.
Updating Xcode project:
🚫 xcodeProject:
-- Caused by: notFound(path: "/Users/<user>")
🛑 Command failed with exit code 1: /Users/<user>/.amplify/lib/aws-amplify-amplify-frontend-ios/resources/amplify-xcode import-config --path=/Users/<user>
Resolution: Please report this issue at https://github.com/aws-amplify/amplify-cli/issues and include the project identifier from: 'amplify diagnose --send-report'
Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/
Session Identifier: fd397e50-186d-4cd3-8af1-efe79881f986
✔ An unexpected error has occurred, opt in to send an error report to AWS Amplify with non-sensitive project configuration files. Confirm (y/N) · no
|
Same here any solution or any hint on what is the issue? It seems for me there is some issue related with Swift Package Manager.
Proposed resolution does not help since I am in a frontend project following multi-frontend approach so there is no backend folder and
|
How did you install the Amplify CLI?
No response
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
12.2.3
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
Amplify CLI throws the error message
The error appears to be due to Xcode not being used. set the terminal as Vscode on init a well.
Expected behavior
provide a better error message
Reproduction steps
amplify init
(with Vscode and ios as config)amplify pull
Project Identifier
No response
Log output
Additional information
No response
Before submitting, please confirm:
The text was updated successfully, but these errors were encountered: