aws-amplify / aws-amplify/amplify-cli

Command failed with exit code 1: in a ios project

Open
#13,064 2 comments 1 reaction 0 assignees View on GitHub
bug good first issue p4 platform-init
Dominant language
TypeScript
Stars
2.9k
Forks
825
Avg merge
11d 23h
Merged PRs (30d)
2

Description

### 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

```
🚫 xcodeProject:
-- Caused by: notFound(path: "")
Command failed with exit code 1: /Users//.amplify/lib/aws-amplify-amplify-frontend-ios/resources/amplify-xcode import-config --path=/Users//Documents/apps/iostest
```

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

1. `amplify init` (with Vscode and ios as config)
2. should see it on init finish or can run `amplify pull`

### Project Identifier

_No response_

### Log output

```
# Put your logs below this line

```

### Additional information

_No response_

### Before submitting, please confirm:

- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.

Contributor guide

Open the contributing guide

Research direction

Reproduce the failure using `amplify init` with VS Code and an iOS configuration, then compare it with `amplify pull`. Start at the `amplify-xcode import-config` command and its reported `notFound` path; done means the CLI gives a clearer error when the expected Xcode project or path is unavailable.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, typescript
Domain
cli, mobile-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.