Back to blog
GuideReact NativeExpoiOSXcodeCI/CDWindows

React Native iOS Build Without a Mac: Expo EAS, CI or a Cloud Mac

November 15, 20268 min readby Macyou Team

React Native’s own setup guide says it plainly: “A Mac is required to build projects with native code for iOS.” So on Windows or Linux you write the app on your PC, and the iOS build runs on a Mac somewhere else. You have three ways to get that Mac: let Expo’s build service (Expo Build, formerly called EAS Build) compile the app in the cloud, run the build on a CI service with macOS runners such as GitHub Actions, or rent a cloud Mac and use Xcode on it. Prices and limits of other companies’ products below were checked on 15 November 2026.

What React Native’s docs say

The setup guide lets you pick your development OS and your target OS. For Windows or Linux with iOS as the target it shows one short note: a Mac is required to build projects with native code for iOS, and “You can use Expo Go from Expo to develop your app on your iOS device.” For macOS it lists what an iOS build needs: Node, Watchman, the React Native command line interface, Xcode and CocoaPods. Xcode runs only on macOS; the Xcode system requirements page lists which Macs qualify.

The JavaScript side of your app does not care about any of this. The Mac is needed for the native iOS project: compiling it, signing it and sending it to Apple.

Three routes side by side

RouteWhere the iOS build runsPrice, checked 15 November 2026FitsLimits
Expo Build and Expo Submit (EAS)macOS runners in Expo’s cloudFree: up to 15 iOS builds a month in a low priority queue. Starter: $19 a month with $45 of build credit; an iOS build costs $2 on a medium workerExpo projects and existing React Native projectsBuilds only, no Xcode window. On the Free plan a build times out after 45 minutes
GitHub Actions macOS runnersMacs hosted by GitHubFree on standard runners in public repositories. Private: $0.062 a minute, with $12 a month of included compute on GitHub FreeTeams on GitHub with scripted buildsBuilds only, no screen. You write the workflow and manage signing yourself
A cloud Mac you rentA dedicated Mac that only you useMacyou M4 Mac mini, 16 GB: $99 a month, or $80 a month billed annuallyBare React Native projects with custom native code; debugging in Xcode, the Simulator and InstrumentsBilled by the month or the year; you install and update the tools

Route 1: Expo Build and Expo Submit

Expo has dropped the EAS prefix from its services, so EAS Build is now called Expo Build and EAS Submit is Expo Submit. The command line tool, the eas.json file and the commands keep the eas name. Expo describes Expo Build as a hosted service that builds app binaries for Expo and React Native projects, and says iOS builds run on macOS runners in Expo’s macOS cloud. It is not limited to apps created with Expo: Expo’s docs say it works with existing React Native projects created with npx react-native init or similar tools.

The first build is a short list of commands on your PC:

  1. npm install --global eas-cli, then eas login with your Expo account.
  2. eas build:configure in the project folder.
  3. eas build --platform ios, which sends the project to Expo’s cloud and waits for the build.
  4. eas submit --platform ios to upload a production build to App Store Connect, or eas build --platform ios --auto-submit to do both in one go.

About the last step Expo’s docs say: “Expo Submit works on macOS, Linux, and Windows, so you don’t need a Mac to ship iOS builds.” After Apple processes the upload, the build appears in TestFlight.

Free tier and paid plans

The Free plan includes up to 15 iOS builds and 15 Android builds a month. They go into a low priority queue, where Expo warns that waits can pass 90 minutes at peak times, and a build times out after 45 minutes. The Starter plan costs $19 a month and includes $45 of build credit and the high priority queue. The Production plan costs $199 a month with $225 of credit. Credit that you do not use does not roll over.

On the paid plans a build has a flat price: $2 for an iOS build on a medium worker and $4 on a large one. The Starter credit therefore covers 22 medium iOS builds. A developer who runs 30 iOS builds a month is past the free 15; on Starter those builds come to $60, which is $15 more than the credit, so the month costs about $34.

The limit is the same as with any build service: you get logs and an app file. There is no Xcode window to step through native code in, and no Simulator on your screen.

Signing with EAS managed credentials

An iOS app has to be signed before it can be distributed, with credentials such as a distribution certificate and a provisioning profile. Expo’s docs say Expo Build can generate and manage iOS provisioning profiles and distribution certificates for you, or use credentials that you provide.

  • Generating the iOS credentials requires you to sign in with an Apple Developer Program membership, which costs $99 a year.
  • On the first build, if you have no provisioning profile or distribution certificate yet, Expo’s setup guide says you can let EAS CLI take care of that by signing in to your Apple Developer Program account and following the prompts.
  • For submissions that run without you, Expo’s guide has you set up an App Store Connect API key through eas credentials --platform ios.

These steps run in EAS CLI, the same tool that starts the build.

What Expo Go can and cannot do on an iPhone today

React Native’s docs point Windows users to Expo Go, an app on the phone that opens your project from the development server on your PC. It lets you see your changes on a real iPhone while you write JavaScript. What it is not is a way to build or ship your app.

  • Expo describes Expo Go as a playground for students and learners, limited and not meant for production projects.
  • Getting it onto an iPhone takes several steps. Expo’s guide asks for an active Apple Developer Program membership, has you build Expo Go with npx eas-cli@latest go, and installs it through TestFlight.
  • On a physical iOS device, Expo Go opens a project only when Expo CLI on the PC and Expo Go on the phone are signed in to the same Expo account.

For a real project Expo points to a development build: a build of your own app that includes Expo’s developer tools. Expo Build compiles it in the cloud. You register the iPhone with eas device:create, run eas build --platform ios --profile development, install the result from a QR code and turn on Developer Mode on the phone. This also needs the Apple Developer Program membership. More ways to see an iOS app from a PC are in iOS Simulator on Windows.

Route 2: GitHub Actions macOS runners

If you do not want Expo’s service, a CI system with macOS runners can run the build. GitHub hosts macOS runners in its own macOS cloud, and a job asks for one with a label such as macos-latest. React Native’s publishing guide describes the release build as Xcode menu steps, so on a runner you script the same build with Apple’s command line tools or fastlane, and you bring the signing certificate and provisioning profile yourself.

Standard runners are free in public repositories. In a private repository a macOS minute costs $0.062, and GitHub Free includes $12 of compute a month, about 193 macOS minutes. A month of 30 builds at 15 minutes each, 450 minutes, costs about $16 on GitHub Free after the included compute. GitHub does not charge for minutes on self hosted runners, and a Mac that you rent can be one, as iOS CI with GitHub Actions on a dedicated Mac shows.

Codemagic is another CI service with Mac machines and a React Native guide. That guide needs the ios project folder, and for Expo projects that do not keep one it runs npx expo prebuild on the build machine. Its prices and signing are covered in Flutter iOS build without a Mac, and Apple’s own CI in Xcode Cloud pricing explained.

Route 3: a cloud Mac, when you need Xcode itself

Build services hand you a finished file. A bare React Native project with custom native code often needs more than that: a native module that will not compile, a crash that only shows in the Xcode debugger, a memory problem you want to see in Instruments, or a layout you want to check in the Simulator. For these you need Xcode on a screen, and from a PC that means a Mac you reach remotely.

Macyou is one example. You rent a dedicated physical Mac mini or Mac Studio by the month or by the year, one customer per machine. Your macOS account is an administrator with sudo, and you install Xcode, Node and CocoaPods yourself; Xcode is not preinstalled. You connect over SSH with a key and see the full screen in Screen Sharing or any VNC viewer on Windows or Linux, over the same secure connection. There is no desktop in the browser. The Mac is ready about 5 minutes after payment is confirmed and runs 24/7. The M4 Mac mini with 16 GB costs $99 a month, or $80 a month billed annually.

The limits: billing is monthly or annual, so for a handful of builds a month Expo’s Free plan costs less. You also install and update Xcode and the rest of the tools yourself.

Steps on the cloud Mac

  1. Connect from your PC over SSH, and open the Mac’s screen in a VNC viewer for Xcode.
  2. Install Xcode and the Xcode Command Line Tools, then Node, Watchman and CocoaPods, the list from React Native’s setup guide. Your administrator account can accept the Xcode licence with sudo.
  3. Clone your project. In its ios folder run bundle install and bundle exec pod install to install the iOS dependencies.
  4. Open the workspace in Xcode, sign in with your Apple ID and run the app in the Simulator while you debug.
  5. For a release, React Native’s publishing guide uses the Release scheme, then Product > Archive, then Distribute App with App Store Connect as the destination.
  6. The build then appears in App Store Connect under TestFlight, and you install it on your iPhone with the TestFlight app.

The routes also combine: you can keep routine builds on Expo Build or CI and use a Mac only for the native work that needs Xcode.

Which one to pick

  • An Expo app, or a React Native app without unusual native code: Expo Build and Expo Submit. Start on the Free plan.
  • Builds that already live in GitHub workflows, with someone on the team who can maintain signing: GitHub Actions.
  • A bare React Native project where you write or debug native iOS code: a cloud Mac, alone or next to a build service.

The wider picture, with native Swift and other frameworks, is in Xcode on Windows. Every Mac we rent is on the pricing page.

Rent a Mac mini for Xcode

Questions

Can I build a React Native iOS app on Windows?

Not on the PC itself. React Native’s docs say a Mac is required to build projects with native code for iOS. From Windows you start the build with EAS CLI and Expo’s cloud compiles it, or you use a CI service with macOS runners or a rented cloud Mac.

Is Expo EAS Build free?

There is a Free plan with up to 15 iOS builds a month, a low priority queue and a 45 minute build timeout. Beyond that the Starter plan costs $19 a month and includes $45 of build credit. Apple’s Developer Program membership at $99 a year is separate.

Do I need a Mac to publish a React Native app to the App Store?

Not with Expo. Expo’s docs say Expo Submit works on macOS, Linux and Windows, so you do not need a Mac to ship iOS builds. Without Expo, the upload runs on a Mac: a CI runner or a Mac you rent.

Can I run my React Native app on my iPhone without a Mac?

Yes, with Expo. Expo Go opens your project on the phone for learning, and a development build made by Expo Build is the route for a real project. Expo’s guide asks for an active Apple Developer Program membership for both.

Sources

All checked on 15 November 2026.