nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

bash: xcodebuild: command not found while setting up iOS (swift) CI/CD pipeline on bitbucket?

Akash Ashok Kondekar

Hello,

I am a newbie on CI/CD bitbucket integration stuff. When I was trying to execute any command related to xcodebuild,(such as clean, build, etc) by specifying it in yml file, it threw me an error "bash: xcodebuild: command not found command not found".

I tried multiple solutions for it but not a single command/Path works for me hence if I get help related to that then that will be helpful or else If I get step-by-step Documentation related to CI/CD iOS with bitbucket integration will also work.

FYI: Checked with the correct Path and required xcodebuild to be in the same directory or not and found they both were at the same level.

Accepted answers

All comments

Theodora Boudale

Hi @Akash Ashok Kondekar,

MacOS Runners use Bash to run pipeline steps on your MacOS machine (host device), so the builds do not run in Docker containers.

What the runner will do for each step is clone the repo on your machine (unless you have disabled cloning in your bitbucket-pipelines.yml file) and then execute the commands from the step's script. The runner will try to empty the build directory after each step.

If a certain tool is installed on your MacOS machine and you can use it from bash, it should be possible to use it with a MacOS Runner.

If you try the following:

open a new terminal on your Mac
clone the repo you want to run builds for
change directory to the clone you created
execute the commands from your bitbucket-pipelines.yml file's script

are you then able to run the failing command this way?

Does the command which xcodebuild return any output?

Kind regards,
Theodora

Akash Ashok Kondekar

Thanks for the reply, @Theodora Boudale

Unfortunately, I am still facing the same issue. Posting screenshots that might help you to understand where I am failing at:

1. yml file: It started failing from line 18, i.e. xcodebuild clean... command

Screenshot_2023-07-10_at_4.04.44_PM.png

2. Output that I can see on bitbucket pipeline console:

Screenshot_2023-07-10_at_4.05.54_PM.png

As I said earlier, I had already committed and can see xcodebuild at the same level directory level where in my installing my pods.

Theodora Boudale

Hi @Akash Ashok Kondekar,

Thank you for the info.

I can see from both screenshots that you are running this Pipelines build on our own infrastructure. You mentioned in the title iOS pipeline, so I thought you were using a MacOS Runner (this is why I was talking about MacOS Runners in my previous post).

Pipelines that run in Atlassian's infrastructure currently run on a Kubernetes cluster of Linux Docker hosts. I believe that it is not possible to run xcodebuild on a computer that is not a MacOS, so I don't think you'll be able to run this build on our own infrastructure.

If you have a MacOS that you can use to run builds, you can set up a MacOS runner on that machine and run builds there:

https://support.atlassian.com/bitbucket-cloud/docs/set-up-runners-for-macos/

The builds will run on your MacOS, but you'll still be able to view the logs on the Bitbucket website on the Pipelines page of the repo. Additionally, you won’t be charged for the build minutes used by your self-hosted runner.

You can see here the Supported platforms and Minimum Requirements for runners:

https://support.atlassian.com/bitbucket-cloud/docs/runners/

Please feel free to let me know if you have any questions.

Kind regards,
Theodora

Akash Ashok Kondekar

Thanks, @Theodora Boudale

Here's a summary of the actions we've tried so far:

Clearing Derived Data
- We attempted to resolve any cached or corrupted build artifacts by clearing the derived data for your Xcode project.

Cleaning Build
- To ensure there are no old artifacts causing conflicts, we performed a clean build by holding the "Option" key and selecting "Clean Build Folder" in Xcode.

CocoaPods Version
- We ensured that we are using the latest version of CocoaPods by running "gem install cocoapods" and updating the pods with "pod update".

Xcode Version
- We confirmed that we are using the latest stable version of Xcode to avoid any bugs or compatibility issues.

Review Pod Configuration
- We reviewed the configurations in the Xcode project after installing the pods to ensure correct integration with the main app target.

Swift Code
- We reviewed your Swift code for any syntax errors or issues that might be causing the compiler to fail.

Pod Dependency Conflicts
- We checked for pod dependency conflicts and updated or removed specific pod versions to resolve any conflicts.

System and Xcode Compatibility
- We verified that your macOS version and Xcode version are compatible with the Swift version and the pods we are using.

Verify Signing and Capabilities*We ensured that the signing and capabilities are correctly configured for the 'DailyMentor' target. This includes checking provisioning profiles, certificates, and any necessary entitlements.

Despite implementing the above steps, we still encounter the same error: ie. " BUILD FAILED The following build commands failed: SwiftEmitModule normal arm64 Emitting\ module\ for\ DailyMentor (in target 'DailyMentor' from project 'DailyMentor') (1 failure)"

PFA screenshots.

I am not sure now what I am missing here.

Hassan Syed_1et96z

This error is expected on Pipelines' hosted runners — they're Linux containers, so `xcodebuild` doesn't exist there, and Bitbucket doesn't offer hosted macOS. The two ways out are a self-hosted macOS runner (a Mac you keep online, per Theodora's links above) or keeping the Linux runner and sending only the Xcode step to a Mac.

For the second option, this is a complete `bitbucket-pipelines.yml` that builds and tests an iOS project from the default Linux image (disclosure: I work on the service it calls, mac.doublespeed.ai):

```yaml

image: node:22

pipelines:

pull-requests:

'**':

- step:

name: iOS build + tests (on a remote Mac)

script:

- npm install -g @doublespeed/ds

- ds xcode test . --destination 'platform=iOS Simulator,name=iPhone 16 Pro'

```

`DS_API_KEY` goes in Repository settings → Repository variables (mark it Secured). The step exits non-zero on build or test failures and prints errors as `file:line:col`, so the pipeline fails the same way a local `xcodebuild` would; add `--json` if you want to parse the results. Native Swift, React Native and Expo projects all work — CocoaPods are installed on the Mac side. Billing is per second of Mac time actually used (a small app's test run is a few cents), which for most teams comes out well under keeping a Mac mini online as a runner.

If you'd rather not depend on a service, the self-hosted macOS runner route works fine too; the important thing is that the hosted Linux runner will never have `xcodebuild`, so no amount of PATH fixing will help.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

bitbucket

bitbucket-cloud