Flutter iOS without a Mac: build, test and publish from Windows or Linux
The short answer: you can do most of Flutter iOS development without a Mac, but not the iOS build. That step runs Xcode, and Xcode only runs on macOS. The good news is that the Mac does not have to be yours, or even in the room.
Below is what works on Windows and Linux, and what does not. Then a GitHub Actions workflow that builds your iOS app on a Mac in the cloud. We ran every command here on October 1, 2026 with Flutter 3.47.5 and Xcode 26.6.
What works without a Mac, and what does not
| Task | Runs on | On Windows or Linux | Mac needed |
|---|---|---|---|
| Write the Dart code | any OS | yes | no |
| flutter test (unit and widget) | the Dart VM, any OS | yes, passed on both | no |
| flutter build ios | macOS with Xcode | not available | yes |
| iOS simulator, Xcode debugging | macOS only | not available | yes |
| Sign and upload to TestFlight | Xcode tools on macOS | not available | yes |
| Install on your iPhone | the TestFlight app | yes | no |
So the Mac is needed for three things: building, simulating and signing. Everything else happens on the machine you already have.
Run your tests on Windows or Linux
flutter test runs unit and widget tests on the Dart VM, not on an iPhone. So it works anywhere Flutter installs. We created a new app and ran its tests on a Windows runner and an Ubuntu runner. Both passed. This is where you should catch most bugs, before any Mac is involved.
flutter create demo cd demo flutter test
Build the iOS app on GitHub Actions
GitHub rents you a Mac by the minute. Push your code and a macOS runner does the iOS build. Here is the workflow. It installs Flutter, builds for the simulator, builds for a device without signing, and produces an archive.
# .github/workflows/ios.yml
name: ios
on: [push, workflow_dispatch]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v5
- uses: subosito/flutter-action@v2
with:
channel: stable
- run: flutter test
build-ios:
runs-on: macos-26
needs: test
steps:
- uses: actions/checkout@v5
- uses: subosito/flutter-action@v2
with:
channel: stable
cache: true
- run: flutter build ios --simulator
- run: flutter build ios --release --no-codesign
- run: flutter build ipa --no-codesignOn the macOS runner, those three builds printed:
✓ Built build/ios/iphonesimulator/Runner.app ✓ Built build/ios/iphoneos/Runner.app (14.4MB) ✓ Built build/ios/archive/Runner.xcarchive (169.6MB) Codesigning disabled with --no-codesign, skipping IPA.
That last line matters. Without signing you get an archive, not an .ipa you can upload. It proves the iOS build works, which catches most iOS-only breakage. To ship, you need signing.
The whole macOS job took about three minutes for a new app. Hosted runners are free on public repositories. On private ones, GitHub bills macOS minutes at about $0.062 each, roughly ten times a Linux minute. So keep the tests on the Linux job.
Publish to the App Store without a Mac
Publishing is the same build with signing turned on. The Mac is still a runner in the cloud. You need three things from Apple first:
With those in place, flutter build ipa without --no-codesign produces a signed .ipa. A tool like fastlane, with its upload_to_testflight action, then sends it to App Store Connect. From there you install it on your own iPhone with the TestFlight app. No Mac and no cable.
When a cloud runner is not enough
A runner is a Mac you never see. That is fine for builds. It is painful when something only breaks on iOS and you need to look at it. You cannot open the simulator, click through the app, or step through it in Xcode on a machine that disappears when the job ends.
For that you need a Mac you can reach. It can be your own, a friend's, or a rented one. A MacRun Mac is a dedicated Mac mini you open in a browser tab, with Xcode and the iOS simulator ready. It can also run your GitHub Actions jobs, with no per-minute bill.
Questions
- Can I build a Flutter iOS app on Windows?
- Not on Windows itself. The iOS build runs Xcode, and Xcode only runs on macOS. You can write the code and run the tests on Windows, then let a Mac in the cloud do the iOS build, for example a GitHub Actions macOS runner.
- Can I run Flutter tests for an iOS app on Windows or Linux?
- Yes, for unit and widget tests. flutter test runs them on the Dart VM, not on an iPhone. We ran the same test suite on Windows and Linux runners and both passed. Tests that drive a real iOS simulator still need a Mac.
- Can I publish a Flutter app to the App Store without a Mac?
- Yes, if a Mac in the cloud does the signed build and upload. You need an Apple Developer account, a distribution certificate and an App Store Connect API key. The macOS runner builds the signed app and uploads it to TestFlight.
- How do I test the iOS app on my iPhone without a Mac?
- Install it through TestFlight. Once a build is uploaded to App Store Connect, the TestFlight app on your iPhone installs it. No Mac or cable is involved.
Run your own numbers on the calculator or lease a runner.