App builds

Overview

Mobile tests run against an app build stored in your project. Builds are kept as Assets in Test data, so any test can use them.

Platform	File
Android	.apk
iOS	.ipa

There is no hard file size limit, but we recommend keeping the built app under 200 MB.

---

Uploading a build

You can add a build in two ways.

While creating a test

You can upload a build without leaving test creation. Open Select mobile app and choose Upload new mobile app at the bottom of the list.

From Test data

1. Go to Test data and open Assets.
2. Click Upload asset.
3. Drag and drop the file, or click to select it.
4. Edit the File name if you want. The name is used to reference the build, so pick something recognizable, like the app name and version.
5. Click Upload.

When you release a new version of your app, upload it as another asset and select it in your tests.

Android

Android is supported natively. Upload your .apk and it works on all supported devices, both real devices and emulators.

iOS

Upload your .ipa and the test runs on iOS devices.

Simulator build for file picker flows

Some flows need an extra build. If your test uses the file picker, for example to upload a document, also provide a Simulator build of your app. On real cloud devices the .ipa is re-signed, which breaks the file picker. Simulator builds are not re-signed, so they avoid the problem.

A Simulator build is the .app bundle built for the iOS Simulator, zipped. For example:

xcodebuild -scheme <scheme> -configuration <configuration> -sdk iphonesimulator -derivedDataPath build

Then zip the resulting .app, which is in build/Build/Products/<configuration>-iphonesimulator/. No code signing or provisioning is needed.

Make sure the Simulator build:

• uses the same configuration and backend environment as your .ipa
• has jailbreak, emulator and anti-tamper detection turned off, if your app has it. Otherwise it blocks the app from launching on the Simulator.