Fruit

A lightweight command-line tool for local iOS simulator development workflows.

Overview

Fruit wraps xcodebuild and simctl so the common edit-build-run loop for an Xcode app can happen from the terminal.

Instead of remembering long xcodebuild and Simulator commands, run:

fruit run

Fruit discovers the current .xcworkspace or .xcodeproj, resolves the scheme, builds for a selected simulator, boots the simulator if needed, reinstalls the app, and launches it.

Features

• List available iOS simulators
• Save a project-local selected simulator in .fruit/config.json
• Save a project-local selected scheme in .fruit/config.json
• Show the selected simulator
• List Xcode schemes for the current project
• Build an app for an iOS simulator using local .fruit/DerivedData
• Build, boot, reinstall, and launch with fruit run
• Open the current Xcode project
• Clean Fruit-managed build output
• Run diagnostics with fruit doctor

Requirements

• Xcode
• Zsh
• Swift toolchain

Installation

Clone the repository:

git clone https://www.github.com/m-tedeschi/fruit.git
cd fruit

Run the installer:

chmod +x install.sh
./install.sh

The installer builds Fruit and copies the executable to:

~/.fruit/bin/fruit

If needed, the installer adds a managed setup block to ~/.zshrc so fruit is on your PATH.

Restart your shell, or reload your shell configuration:

source ~/.zshrc

Verify the installation:

which fruit

Expected output:

/Users/yourname/.fruit/bin/fruit

Usage

Command	Description
fruit	Show help.
fruit version	Show the installed Fruit version.
fruit --version	Show the installed Fruit version.
fruit devices	List available iOS simulators.
fruit device	Show the selected simulator.
fruit device <device>	Select a simulator by name or UDID.
fruit schemes	List Xcode schemes for the current project.
fruit scheme	Show the selected scheme, or the inferred scheme when only one exists.
fruit scheme <scheme>	Select an Xcode scheme.
fruit build	Build for the selected simulator.
fruit build <device>	Build for a specific simulator without changing the selected simulator.
fruit build --verbose	Build and stream raw xcodebuild output.
fruit build --o output.log	Save raw xcodebuild output to .fruit/output.log.
fruit run	Build, boot, reinstall, and launch on the selected simulator.
fruit run <device>	Build, boot, reinstall, and launch on a specific simulator.
fruit run --verbose	Run and stream raw xcodebuild output during the build phase.
fruit run --verbose --o output.log	Stream output and save the build log to .fruit/output.log.
fruit clean	Remove .fruit/DerivedData.
fruit open	Open the current project in Xcode.
fruit doctor	Check whether Fruit can build and run the current project.
fruit logs	Omitted from version 1.0.1.

Fruit resolves simulator devices in this order:

1. device argument, if provided
2. saved device in .fruit/config.json, if valid
3. exactly one booted simulator, if present
4. fail with a message suggesting fruit devices or fruit device <device>

Fruit resolves schemes in this order:

1. saved scheme in .fruit/config.json, if valid
2. exactly one available scheme
3. fail with a message suggesting fruit schemes or fruit scheme <scheme>

Fruit prefers a single .xcworkspace when one exists, which supports common CocoaPods projects. If there is no workspace, Fruit falls back to a single .xcodeproj.

Fruit reads shared scheme files directly from the selected project or workspace when possible, and falls back to xcodebuild -list only when no shared schemes are found.

Version 1.0.1 supports simulator devices only. It expects exactly one .xcworkspace or exactly one .xcodeproj in the current directory tree.

Future Improvements

• Add fruit logs for streaming logs from the launched app
• Add explicit simulator controls such as boot, shutdown, and uninstall