ios-build-automation

Build Automation & SweetPad Integration

CRITICAL: This file defines how the LLM should use build automation tools (SweetPad/xcodebuild) to verify code changes automatically in agent mode.

Purpose

When in agent mode, the LLM must automatically verify builds and tests after code changes. This ensures:

• Zero-warning policy enforcement
• Test verification before marking work complete
• Immediate error detection and fixing
• No manual build verification required

---

SweetPad Build Commands

Physical Device Build Command

Current Configuration:

• Device ID: {{DEVICE_ID}} (physical iOS device)
• Workspace: {{WORKSPACE_PATH}}
• Scheme: {{SCHEME}}
• Configuration: Debug

Set these via a project-specific rule, env vars, or .xcode.env. Example: export DEVICE_ID=... WORKSPACE_PATH=... SCHEME=... RESULT_BUNDLE_PATH=... and use $DEVICE_ID, $WORKSPACE_PATH, etc. in the commands below.

Build Command:

xcodebuild \
  -scheme {{SCHEME}} \
  -configuration Debug \
  -workspace {{WORKSPACE_PATH}} \
  -destination 'platform=iOS,id={{DEVICE_ID}}' \
  -resultBundlePath '{{RESULT_BUNDLE_PATH}}' \
  -allowProvisioningUpdates \
  build

Test Command:

xcodebuild \
  -scheme {{SCHEME}} \
  -configuration Debug \
  -workspace {{WORKSPACE_PATH}} \
  -destination 'platform=iOS,id={{DEVICE_ID}}' \
  -resultBundlePath '{{RESULT_BUNDLE_PATH}}' \
  -allowProvisioningUpdates \
  test

Notes:

• -allowProvisioningUpdates enables automatic code signing/provisioning
• Result bundle path is SweetPad-specific and may change with workspace storage
• Device ID can be obtained via: xcrun xctrace list devices
• Update device ID if physical device changes

---

Alternative: Simulator Build (Fallback)

If physical device is unavailable or for faster iteration, use iOS Simulator:

Simulator Build Command:

xcodebuild \
  -scheme {{SCHEME}} \
  -configuration Debug \
  -workspace {{WORKSPACE_PATH}} \
  -destination 'platform=iOS Simulator,name=iPhone 16' \
  build