Zilmac Blog
← Back to Tech Practice

Claude Code on Windows for iOS: which Mac runs the build and signing

iOS development ·About 9 min read

Claude Code on Windows editing an iOS repo; build and signing run on a remote Mac

Claude Code can live in a Windows terminal: edit Swift/UIKit, tidy Git messages, and maintain Podfile or SPM manifests. Shipping an App Store–ready ipa still requires xcodebuild, keychain signing, and the iOS Simulator on a Mac with Xcode. Below is a clear split of who edits code and who produces the build, so you do not assume Archive works on Windows.

For which machine runs compile, sign, and Simulator, see How do you do iOS development without a Mac. To see whether 16GB holds for Release packaging, use the three-day trial on the same flow.

2 machines
Windows edit, Mac build
1 keychain
Production key on one Mac
By the day
Archive first; ticket after payment

What Claude Code can do on Windows

On Windows, Claude Code fits the daily workstation: read the repo, change Swift/Objective-C, maintain Podfile and SPM lists, draft Fastlane scripts, and run checks that do not need the iOS SDK. Source is just text—it is not tied to macOS.

Claude Code can also draft xcodebuild commands locally, but those commands cannot run iOS destinations on Windows. If the agent says “build succeeded,” check whether it only ran lint or Linux Swift—not an iOS target.

Three steps that cannot stay on Windows

StepMust be on MacCommon Claude Code mistake on Windows
Link against iOS SDKxcodebuild + iOS destinationUsing Linux Swift and assuming it counts
codesign / ArchivePrivate key in Mac keychainExporting p12 to Windows to sign
iOS SimulatorSimulator process on macOSUsing an Android emulator instead
One-line boundary

Claude Code on Windows edits and commits; to get an ipa, always hand the same Git commit to a Mac and Archive there.

Hand off the repo: Git and rsync

Git is the default: git push from Windows, git pull on the Mac, then build from a clean tree. Claude Code is useful before push to fix commit messages and catch accidental xcuserdata commits.

rsync / scp: For air-gapped or tiny teams, rsync -avz --delete can mirror the repo. Exclude DerivedData, .build, and Pods if the Mac will run pod install locally.

  • Keep lockfiles in version control: Podfile.lock, Package.resolved.
  • *.mobileprovision files usually stay out of Git; install them on the Mac or in CI secrets.
  • Case sensitivity: Windows is loose, macOS is strict—Claude Code renames must match Xcode targets.

Trigger compile and Archive over SSH

Windows terminal SSH into a Mac to run xcodebuild Archive remotely
SSH from Windows into the Mac and run xcodebuild in the repo; Claude Code can draft and sanity-check commands, but execution stays on macOS.

With Remote Login enabled on the Mac, ssh user@mac-host from Windows opens a packaging session. A typical pipeline:

On the Mac (via SSH)
cd ~/ios-app && git pull --ff-only
xcodebuild archive \
  -scheme YourApp \
  -configuration Release \
  -destination 'generic/platform=iOS' \
  -archivePath build/YourApp.xcarchive

Claude Code on Windows can maintain this script and update scheme names, but you run it inside SSH. After Archive, export ipa or upload via Xcode Organizer or xcodebuild -exportArchive.

For connection details, see SSH and VNC in the Help Center.

Signing and the keychain stay on that Mac

Apple expects codesign on the Mac that holds the private key:

  1. Create the distribution cert in Apple Developer; generate CSR and install the key on the packaging Mac.
  2. Use automatic signing or Fastlane match, but production keys still live only on the Archive machine.
  3. Do not store production p12 on Windows; do not paste private keys into Claude Code logs.

Compile and sign must complete on the same Mac—without the private key there, export fails at Archive time. See the signing section in iOS development without a Mac.

A typical day of back-and-forth

TimeWindows + Claude CodeMac
MorningUI fixes, bugs, local git commitIdle or shared
Before lunchgit pushgit pull, unit tests
AfternoonNext feature branchRelease Archive, TestFlight upload
Need UI checkRead logs, screenshotsRun Simulator; remote via VNC (separate article)

If you Archive more than once per day, note whether 16GB slows compile with Simulator open—log times in the three-day trial on your real project.

Do not mix certificates on a shared desktop

On a shared remote Mac, another person’s profiles and login items sit in the same user. Claude Code on Windows only changes your source, but signing uses whatever cert is in the currently logged-in Mac keychain. Solo developers should use a Mac with only their certs; shared setups need separate users or instances so you do not Archive under someone else’s team.

Where to go next

Run the loop on 16GB billed by the day: push on Windows → pull on Mac → SSH Archive → signing passes. Then decide on monthly rental or buying hardware.

Open pricing, pick 16GB, billed by the day. After payment, the order enters a ticket.

Sources

FAQ

Can Claude Code Archive iOS directly on Windows?

No. Claude Code can edit the repo and run scripts, but the iOS SDK, Simulator, and codesign ship with Xcode on macOS only. Archive must run on a Mac.

Can I keep the private key on Windows and only compile on the Mac?

No. Signing reads the private key in the Mac keychain. Install the distribution cert and key on the Mac used for packaging, not on Windows.

When handing off with Git, should DerivedData sync too?

No. Sync source and lockfiles only. Let the Mac generate DerivedData locally.

If several people share one packaging Mac, will Claude Code changes mix certificates?

Yes, if they share one user profile and provisioning profiles pile up. Use a Mac with only your certs, or split logins or machines per person or repo.

16GB · by the day

Ticket after payment

Edit with Claude Code on Windows, Archive on a Mac—run one loop billed by the day.

Open pricing
Limited offer View plans