iOS builds & testing
You choose what to run — job type, target and OS version. MacOps provisions and scales the hardware, and runs every job in a clean, isolated macOS VM.
Job types
- Build — compile the scheme. Produces the built
.appas an artifact. - Test — build & run your test plan on a simulator. Produces a
.xcresultbundle with results & coverage. - Archive — produce a signed
.ipayou can download (uses your managed signing certificate). - Deploy — archive, sign and upload to TestFlight. See Signing & TestFlight.
Targets
- iOS Simulator — fast, cheap; for builds and tests. MacOps picks an available simulator inside the VM.
- Physical iPhone — on-device testing on a leased pool device (Team plan). The device is erased after your lease.
- macOS VM — a clean macOS environment for generic build jobs.
OS & Xcode versions
Pick a macOS image (Tahoe 26, Sequoia 15, Sonoma 14, Ventura 13 — each with Xcode) and an iOS version for simulator/device jobs. The scheduler matches your build to a runner that satisfies the version matrix.
Test results & coverage
Test jobs report a pass/fail summary and line coverage right on the build page, and attach the full .xcresult bundle as a downloadable artifact (open it in Xcode for the complete report).
Project environment & secrets
Add per-project variables and secrets (Project → Variables). Secrets are encrypted at rest and injected into the build environment only inside the ephemeral VM.