Blogs on no code mobile apps | Choicely

How to Publish an iOS App Without a Mac (2026)

Written by Aapo Suhonen | Aug 3, 2026, 11:45:48 AM

You can build, sign and publish an iOS app to the App Store without ever owning a Mac. Cloud build services compile your app on their hardware and upload it for you, and Apple sells its developer membership to anyone with a browser. The part almost nobody tells you: since 28 April 2026 some of the cheapest options recommended online can no longer produce a build the App Store will accept — including the cheapest cloud Mac we could find. You usually discover this after you have paid.

This guide covers the six routes that work in 2026, what each actually costs, and the one check to run before you spend anything. If you want the submission steps themselves rather than the choice of route, we cover those separately in how to publish your app to the App Store.

First, the rule that invalidates most advice you will read

Apple requires that apps uploaded to App Store Connect from 28 April 2026 onwards are built with Xcode 26 or later, using an iOS 26 SDK. This applies to new apps and to updates. Apps already on the store keep working and do not need recompiling.

That sounds like a detail for developers. It is actually the thing that decides which cloud Mac you can rent, because Xcode 26 will not install on an old macOS:

  • Xcode 26.0 needs macOS Sequoia 15.6 or later.
  • Xcode 26.4 and later need macOS Tahoe 26.2 or later. Version 26.6 is current at the time of writing.
  • macOS Tahoe 26 is the last macOS to support Intel Macs at all, and it supports only four Intel models: the 2019 Mac Pro, the 2019 16-inch MacBook Pro, the 2020 13-inch MacBook Pro with four Thunderbolt 3 ports, and the 2020 27-inch iMac. macOS 27 will require Apple silicon.

Put those together and a cheap Intel Mac in the cloud, or any rented Mac left on an older macOS, is a machine that cannot ship an app. The build may well succeed. The upload is what fails.

Run this check before you pay for any cloud Mac. Ask the vendor two questions: which macOS version does it run, and which Xcode version is installed? If the answer is anything below macOS 15.6 with Xcode 26, walk away. Prefer macOS Tahoe 26.2 or later, because that is what current Xcode releases need — and an Intel machine can only get there if it is one of the four models above.

We checked the top-ranking guides for this question in August 2026. None of the ones we read mentions this requirement — including one published by a company that rents out cloud Macs.

The six routes, compared

Prices as observed on 30–31 July and 3 August 2026, in whichever currency each vendor quotes. Most of these vendors publish no last-updated date on their pricing pages, so treat every figure as a starting point to verify rather than a quote.

Route Cost Mac needed? Best for
Expo EAS Free tier: 15 iOS builds/month (hard limit, 45-min build timeout) No React Native and Expo projects
Codemagic 500 free macOS minutes/month, then $0.095/min No Flutter and React Native teams
GitHub Actions ≈200 usable macOS minutes/month free, then $0.062/min No Repos already using Actions
Cloud Mac rental From ≈€2.64 for 24 hours; $59–$109/month dedicated — check the macOS version first, the cheapest tiers are often Intel or an old macOS Rented One-off builds, or full Xcode access
Xcode Cloud 25 compute hours/month free with the $99 membership Yes, to set up Teams who already own one Mac
Managed publishing No Xcode, no build config at all No Anyone who does not want to run a toolchain

All of them sit on top of one fixed cost: the Apple Developer Program at $99 per year, which you can buy from any browser on any operating system. We break down that and the Google Play side in what it actually costs to publish an app.

Cloud build services: the genuinely Mac-free route

This is the route to start with. You write code on whatever machine you have; the service compiles it on real Mac hardware it owns and uploads the result to App Store Connect. Expo's own documentation is unusually direct about it: EAS Submit works on macOS, Linux and Windows, so you do not need a Mac to ship iOS builds.

Three services worth knowing, with the details that actually change the decision:

  • Expo EAS — the free tier includes 15 iOS builds per month, enough to validate an app and ship a first release. It is a hard limit with no way to buy extra builds on that tier, and free builds queue at low priority with a 45-minute timeout, which a large app can exceed. Best fit if you are already building with React Native or Expo.
  • Codemagic — 500 free macOS build minutes per month on personal accounts, reset on the 1st; then $0.095 per minute. An iOS build typically runs five to eight minutes, so the free tier is a real allowance rather than a teaser. Note the free minutes do not apply to team accounts.
  • GitHub Actions — the headline "2,000 free minutes per month" is misleading for iOS work, and several guides repeat it uncorrected. macOS runners consume included minutes at a 10× multiplier, so 2,000 included minutes buys roughly 200 real macOS minutes — about 25 to 35 iOS builds. After that it is $0.062 per macOS minute. In its favour: its macos-latest image moved to macOS 26 over June and July 2026 and its default Xcode became 26.6 on 21 July, so it is already past the requirement above with no vendor interrogation needed.

Renting a Mac in the cloud

Renting gives you the full Xcode application over a remote desktop — useful if you need the iOS Simulator, or to sign in to something interactively. Two things to know before you compare prices.

Hourly rental is far cheaper than the monthly plans everyone recommends. Scaleway's M1-M was €0.11 per hour with a 24-hour minimum billing period, which works out at about €2.64 for a full day — against $59 to $109 a month for the dedicated plans that dominate search results. Scaleway is also the only vendor we found whose terms commit to shipping the latest Xcode version compatible with the operating system, which is precisely the problem described above. AWS offers EC2 Mac at $1.23 per hour for mac-m4, also with a 24-hour minimum ($29.52) — but its images ship with no Xcode installed, so a multi-gigabyte download eats into the day you paid for.

Check the macOS version, and check stock. The cheapest cloud Mac we found was $24.99 a month — running macOS Monterey, which cannot run Xcode 26, so nothing built on it can be uploaded at all. Meanwhile several popular budget hosts were sold out or waitlisted when we checked, Hetzner no longer offers Macs, and Azure has no macOS machines. A list of vendors is not the same as a list of vendors you can actually rent from today.

Xcode Cloud looks like the obvious answer. It is not — if you have no Mac

Apple runs its own cloud build service, and it is genuinely generous: 25 compute hours a month are included with the $99 Developer Program membership, with paid tiers from $49.99 a month for 100 hours. If you are looking for a way to build iOS apps in the cloud, it should be the first thing you find.

But Apple's own requirements are explicit: you need Xcode 15.0 or later and a Developer Program membership, and you get started by configuring a workflow in Xcode. Xcode runs only on macOS. So Apple's cloud build product cannot be set up without access to a Mac at least once.

That makes Xcode Cloud excellent if your team already owns one Mac and wants to stop building on it — and no help whatsoever if the reason you are reading this is that you own none. It is worth knowing before you spend an afternoon on it.

Or skip the toolchain completely

Every route above solves the Mac problem and leaves you owning three others, permanently:

  • The Xcode treadmill. April 2026 was not a one-off. Apple raises the minimum SDK roughly every year, and each rise re-invalidates whichever cheap machine or pinned image you settled on.
  • Certificates and provisioning profiles. EAS and Codemagic automate a lot of this, but the Apple credentials, the expiry dates and the failures at 11pm are still yours.
  • Rejection risk. Generated and template-based apps run into App Store Guideline 4.2.6, which rejects them unless the app is submitted by the provider of its content. We wrote about where that stops the whole AI-generated-app category in can ChatGPT build a mobile app?

Choicely takes a different shape. You build your app in the browser, and the Publish Assistant submits it to the App Store and Google Play under your own developer accounts — so you own the apps and the listings, while the build machinery is our problem. There is no Mac, no Xcode, no CI configuration and no SDK deadline in your calendar. When Apple moves the minimum SDK again, nothing on your side changes.

It also lines up with 4.2.6 rather than against it: the app is submitted by the party that owns its content, which is what the guideline actually asks for. If you would rather hand the whole thing over, that is our app publishing service.

What still needs a Mac

Being straight about the edges, because most guides are not:

  • Setting up Xcode Cloud, as above.
  • Free provisioning — installing an app on your own iPhone without a paid membership is an Xcode feature, so it needs a Mac. With the $99 membership and a cloud build service you do not need it.
  • Interactive debugging on the iOS Simulator. Cloud builds give you a binary and a log, not a debugger. A short hourly Mac rental covers this when you need it.
  • Some native modules and unusual build configurations are easier to diagnose with Xcode open in front of you.

None of these blocks shipping. All of them are reasons a €2.64 day of rented Mac is a useful thing to know about.

One route we will not describe

You will see suggestions to install macOS in a virtual machine on a Windows PC. The macOS Software License Agreement permits the software only on Apple-branded hardware, and permits virtualisation only on Mac hardware you own or control. That makes it a licence breach rather than a clever shortcut, so we are not going to write the instructions. The €2.64 rental is legitimate, supported, and cheaper than the risk.

Google Play was never like this

Worth stating plainly, because it is easy to assume the two stores work the same way: Android has never required Apple hardware. The tooling runs on Windows and Linux, it is free, and Google does not enforce an equivalent SDK-version gate at upload. The entire no-Mac problem is Apple's alone.

Android has its own traps instead — a new personal developer account must run a closed test with at least 12 testers for 14 days before it can publish publicly. The steps are in how to publish your app on Google Play.

So which route should you pick?

  • Shipping a React Native, Expo or Flutter app: start with Expo EAS or Codemagic. Free tiers cover a first release, and neither needs a Mac at any point.
  • Already on GitHub Actions: use it — it is already on macOS 26 with Xcode 26.6. Just budget on ≈200 macOS minutes, not 2,000.
  • Need Xcode itself, briefly: rent hourly. Roughly €2.64 for a day beats every monthly plan, and ask the two questions first.
  • Already own one Mac: Xcode Cloud's 25 free hours a month is the best value on this page.
  • Don't want a toolchain at all: a managed publishing service removes the Mac question, the Xcode question and the SDK-deadline question together.

Whichever you choose, the submission itself is the same on the other side — and we walk through it step by step in how to publish your app to the App Store, including how long review takes once you hit submit.