Keep the editor on the computer you already use. A build that can be installed on an iPhone, the signature, and the simulator all happen on one Mac that has Xcode installed. This page says which machine does each step, and why those three steps stay together.
Which machine does each step
Separate “edit the project” from “produce an installable build.” Source files are not tied to an operating system. The iOS SDK, the private key in the keychain, and the simulator process are tied to macOS.
| Task | Machine | Why |
|---|---|---|
| Edit Swift, assets, and Git | The computer you use now | Source is text and asset files |
xcodebuild / Xcode compile | A Mac with Xcode | The iOS SDK ships only with Xcode on macOS |
| Signing, profile, private key | That same Mac | codesign reads this machine’s keychain |
| iOS Simulator | That same Mac | Simulator is a macOS process shipped with Xcode |
| Store listing title and screenshots | Any browser | Metadata does not go through the compiler |
| Upload the build | That same Mac | Xcode and Transporter both run on macOS |
The daily computer edits code. Build, signing, and the simulator stay on one Mac, so the certificate and the simulator process are not split apart.
The build runs only on a Mac with Xcode
Opening the project, changing a button, and committing to Git all work on Windows or Linux. Compiling an iOS app links the iPhoneOS or iPhoneSimulator SDK. Both SDKs are installed with Xcode and exist only on macOS. Apple’s Xcode download page offers that toolchain as a Mac app.
The Swift toolchain on Linux can compile Swift programs for a server. It does not include the iOS SDK, and it cannot produce a build that installs on an iPhone. Writing the code on one machine and compiling the app on another is the normal split.
xcodebuild \ -scheme App \ -destination 'generic/platform=iOS Simulator' \ -configuration Debug \ build
Run that command on the Mac. The daily computer only has to sync the repository. Do not copy the whole DerivedData folder back and forth.
Signing uses that Mac’s keychain
Signing is not finished by dragging a file onto another computer. Automatic or manual signing both end by using the certificate’s private key in this Mac’s keychain. The provisioning profile is installed on this machine too. It records which devices and which App ID this build allows. Apple’s certificate overview puts the certificate and the private key on the Mac that signs.
Build and signing therefore belong on the same Mac. A build made on a machine that does not hold the private key will fail at the signature. Windows has neither this keychain nor codesign.
When one person starts out, the certificate stays on this one Mac. Do not export another copy into a second login just to save a step. Moving machines means installing the keychain and the Xcode version again.
The simulator is a process on that Mac
The iOS Simulator is not an app inside the phone, and it is not a program you install on Windows by itself. It is installed with Xcode, and the process runs on macOS. The launch screen, a tap through a flow, and the console log are all watched on this Mac. Xcode’s documentation puts both “run in Simulator” and “run on a device” inside Xcode on a Mac.
The build can go over SSH: run xcodebuild on the Mac, and the simulator comes up with it. The picture stays on this Mac’s desktop. If you are not sitting at the machine, seeing the simulator window means connecting to this Mac’s graphical desktop. This page only fixes the location: the process is not on your Windows PC.
How the two machines split a day
- Daily computer: editor, Git, and the issue tracker. Push when the change is ready.
- The Mac: pull that same commit, and compile with a fixed Xcode version. Sign with the certificate already in this keychain. Open the simulator on this machine and check the build you just made.
- When the build goes to testers or the store: export the ipa on this Mac and upload it from here. Store listing text can be edited later in any browser.
How the code reaches the Mac
Hand over one commit with Git. On the Mac, git pull and then compile, so the build is the revision you just pushed. Do not sync the whole project folder through a file-sync drive. Derived data, xcuserdata, and local paths travel with it, and the next build will not match.
The certificate, DerivedData, and the simulator runtime stay in one place. Another machine means installing that environment again, and the three results stop matching.
Start with 16GB, billed by the day
Reduce the check to one question: can each of the three steps succeed once on the same Mac? The build finishes, the signature passes, and the simulator opens the build you just made. Whether you need more memory is answered by whether the system stops the compile while the simulator is open. This page does not settle 16GB against 24GB. The starting point is 16GB, billed by the day.
Open the pricing page, choose 16GB, billed by the day. After payment, the order enters a ticket. Follow provisioning in that ticket.
Sources
- Xcode is offered as a Mac app: developer.apple.com/xcode
- Certificates are installed on the Mac that signs: Certificates overview
- Simulator and device runs both start from Xcode on a Mac: Running your app in Simulator or on a device
- Swift on Linux does not include the iOS SDK: swift.org/install/linux
Questions
The editor is on Windows. Can Xcode be installed there too?
No. Xcode is published as a macOS app. The iOS SDK, the simulator, and codesign come with that toolchain and are not on Windows.
Can one machine compile and another machine sign?
Signing reads the keychain that holds the private key. If that key is not on the machine, signing fails. Keep the build and the signature on the same Mac.
Can the simulator be installed on the everyday Windows PC?
No. The simulator is a macOS process installed with Xcode on the Mac. The everyday computer keeps the editor.
Does the store upload also have to happen on this Mac?
Uploading the build happens on macOS, with Xcode or Transporter on this Mac. The title, description, and screenshots can be edited in a browser.