# Build an iOS app for cloud testing: a zipped Simulator .app

> Testsy runs iPhone and iPad tests on an iOS Simulator build. The xcodebuild, Expo and Flutter commands that make one, how to zip it, and what to do in CI.

By Jason Nguyen, Founder, Testsy. Published 2026-11-21. https://testsy.dev/blog/build-an-ios-app-for-testing/

## Not the .ipa

The build you send to TestFlight is an `.ipa`, signed for physical iPhones. Testsy's iPhone and iPad runs need a build for the **iOS Simulator** instead: the `.app` folder, zipped. From [the app docs](https://testsy.dev/docs/apps/): on a Mac, right-click the `.app` and choose Compress, or let the command-line tool zip it for you.

A Simulator build needs no signing certificate and no provisioning profile, which makes it simpler to produce in CI than the release build.

## Native Xcode

```sh
xcodebuild -scheme MyApp -sdk iphonesimulator -configuration Debug -derivedDataPath build
cd build/Build/Products/Debug-iphonesimulator && zip -qry ../../../../MyApp.app.zip MyApp.app
```

That is the command from the docs' CI example. A Release configuration for the simulator SDK works too.

## Expo and React Native

For Expo with EAS, a build profile with `"ios": { "simulator": true }` produces a Simulator build you can download or pass to Testsy as a link. For a bare React Native project, use the `xcodebuild` command above against the workspace. As on Android, use a build that has its JavaScript bundled in, so it does not need Metro running on your machine.

## Flutter

Flutter's own docs say the iOS Simulator [runs only in debug mode](https://docs.flutter.dev/testing/build-modes). So for Flutter, the iOS build to upload is the debug Simulator build:

```sh
flutter build ios --simulator --debug
```

It lands in `build/ios/iphonesimulator/Runner.app`. Zip it as above.

## Upload it

- **In the app:** **App builds → Upload a build**, or from the App line while writing an app test.
- **From CI:** `node testsy-ai.mjs run --project p_… --build MyApp.app.zip`, which uploads (unless that exact file is already there), waits for the check and runs the app's tests. The tool also accepts the `.app` folder and zips it.
- **From a coding agent:** over MCP, with signed upload links. See [Let your coding agent test the mobile app it built](https://testsy.dev/blog/let-your-coding-agent-test-the-mobile-app-it-built/).

Each build is checked on arrival for its bundle id, version and build number and whether our devices can run it. Builds can be up to 1 GB.

## Save the macOS minutes

A Simulator build of a large app can take 30 to 60 minutes of macOS CI. If your native code has not changed, the build has not either: store a fingerprint with each upload and skip the build when it matches. [Test an Expo app in CI without rebuilding](https://testsy.dev/blog/test-an-expo-app-in-ci-without-rebuilding-every-time/) shows how, and the same works with your own hash for native projects.

This post is part of [Mobile release testing: a guide for app teams](https://testsy.dev/blog/mobile-release-testing-for-app-teams/).
