Build and ship iOS apps without owning a Mac
For teams that write apps in React Native, Expo, Flutter, Unity or .NET MAUI on Windows or Linux. The shared code builds anywhere, but the iOS build, code signing and the upload to App Store Connect need Xcode, and Xcode only runs on macOS. A dedicated Mac mini in the datacenter takes over those steps, as a build host your developers reach over SSH and as a runner in your CI.
What this solves
Xcode only runs on macOS
Apple's macOS licence only permits macOS on Apple hardware, so the iOS build step needs a real Mac. A hosted Mac mini covers it without buying Macs for the whole team.
Signing and uploads in one place
Certificates, provisioning profiles and the App Store Connect API key live on one machine you manage, instead of on several laptops.
Builds and debugging on demand
Release builds run from your pipeline. When an iOS-only bug needs a closer look, a developer can open the iOS Simulator on the Mac.
Example workflow
A React Native team on Windows releases to TestFlight
- 1
A developer merges a release branch on GitHub or GitLab.
- 2
The CI job runs on the hosted Mac and installs the JavaScript dependencies and CocoaPods.
- 3
xcodebuild archives the app with the distribution certificate from the runner keychain.
- 4
fastlane uploads the build to App Store Connect with the team's API key.
- 5
Testers receive the build in TestFlight once Apple has processed it.
Which steps need the Mac
Most of the work stays on your Windows or Linux machines. The Mac takes over the steps that require Xcode.
| Framework | Without a Mac | On the Mac |
|---|---|---|
| React Native and Expo | Without a MacJavaScript and TypeScript code, Android builds | On the MacNative iOS build, CocoaPods, signing, simulator, local EAS builds |
| Flutter | Without a MacDart code, Android, web and desktop builds for your own OS | On the Macflutter build ipa, iOS Simulator, signing and upload |
| Unity | Without a MacEditor work and exporting the Xcode project for the iOS target | On the MacBuilding, signing and archiving the exported Xcode project |
| .NET MAUI | Without a MacShared code, Android and Windows builds | On the MaciOS builds through the Mac build host over SSH, signing |
Cloud build services are an alternative. A dedicated Mac fits when you want to choose Xcode versions, keep caches warm and hold credentials on a machine you control.
How to set it up and run it
- 1
Choose the macOS version that supports the Xcode release your framework requires. React Native, Flutter, Unity and .NET MAUI each document a minimum Xcode version.
- 2
Install Xcode, the command line tools and your framework toolchain: Node and CocoaPods for React Native, the Flutter SDK, Unity Hub, or the .NET SDK with the MAUI workload.
- 3
Register the Mac as a self-hosted runner in your CI system, or let developers build over SSH. Use a dedicated macOS user for automated builds.
- 4
Create an App Store Connect API key and keep signing certificates in a separate keychain, or fetch them per build with a tool such as fastlane match.
- 5
For Unity, build the iOS target on Windows or in CI to produce an Xcode project, then build, sign and archive that project on the Mac.
- 6
Install simulator runtimes only for the iOS versions you test, so they do not fill the disk.
Which configuration fits
Mac mini M6
- 12-core CPU · 12-core GPU
- Memory: 16 GB
- Storage: 512 GB SSD
Good fit for
One pipeline building a single app at a time.
€140/moBilled yearly, excl. VAT
Who does what
vBoxx provides
- A dedicated Mac mini M6 or M5 Pro as build host, with the macOS version that matches your Xcode release
- Full admin access over SSH, so CI runners, Visual Studio or your developers can connect from Windows and Linux
- Persistent SSD storage for CocoaPods, Swift packages, build caches and simulator runtimes
- Network: 10 Gigabit Ethernet port · 1 Gbit/s unmetered · public IPv4 + IPv6
- Remote APC power control included, JetKVM console optional
You manage
- Xcode, the framework toolchain and their updates
- Apple Developer Program membership, certificates, profiles and API keys
- CI runner registration and build scripts
- SSH keys, VPN and access for your team
- Licences for tools such as Unity or Visual Studio
Before you choose this setup
- Physical iPhones and iPads cannot be connected to the hosted Mac. Test on your own devices through TestFlight, or use a device cloud.
- Live debugging on a physical device from your Windows or Linux machine is not part of this setup. The hosted Mac covers builds, signing, uploads and the simulator.
- If you build only a few times a month, a cloud build service billed per build may cost less. A dedicated Mac fits regular builds and teams that want control over Xcode versions, caches and credentials.
Questions about cross-platform iOS builds
Xcode, the iOS SDK and Apple's signing tools only run on macOS, and Apple's macOS licence only permits macOS on Apple hardware. Every iOS build passes through a Mac at some point, whether in a cloud service or on a machine you control.
Yes. You can run Expo's local iOS builds (eas build --local) or a plain Xcode build on the Mac. Expo's own cloud build service is a separate product; you choose what fits your workflow.
Yes. Unity on Windows can produce the Xcode project for the iOS target. That project is then transferred to the Mac or built there by CI, where Xcode compiles, signs and archives it.
Use fastlane or Apple's command line tools with an App Store Connect API key. The key belongs to your Apple Developer account; store it as a CI secret or in the runner keychain.
Not through the hosted Mac. Physical devices are not connected in the datacenter. Install builds on your own devices through TestFlight, or use a device cloud.