Import app builds from EAS, Bitrise or S3 by link
If your pipeline already stores the APK or zipped .app somewhere, give Testsy the link. It fetches the build, checks it and runs the app's tests, with no upload step.

The build is already somewhere#
Most mobile pipelines already store their builds: an Expo EAS artifact, a Bitrise or Buildkite artifact, a GitHub Actions artifact, an object in S3 or R2. Downloading it in CI only to upload it again wastes time and bandwidth.
Pass the link#
From app builds from CI:
node testsy-ai.mjs run --project p_myproject --build https://expo.dev/artifacts/eas/….apknode testsy-ai.mjs build import "https://…/MyApp.app.zip?X-Amz-Signature=…" --project p_myproject --header "Authorization: Bearer $STORE_TOKEN"Testsy fetches the file itself (https only, to a public host name, up to 3 redirects, up to the 1 GB build size limit) and checks it like an upload: bundle id or package name, version, build number, and whether our devices can run it.
- Signed links (S3, R2, most artifact stores) need nothing else.
- Private stores: add
--headerwith anAuthorizationorX-…header, at most five. Headers are sent to the first host only. - The file name comes from the link or its
Content-Disposition, and must be an.apkor a zipped.app.
Over MCP, an agent uses import_build with the link and headers.
A build link on the test itself#
A test can also hold a build link (buildUrl): an https link to the build, downloaded on every run. Useful when your store always serves the latest build at the same address, such as a nightly channel.
Which build each test runs#
By default a test runs its app's newest build. You can pin one (Always a chosen version), or override it for one run with --build. Each app test gets the build of its own app, so one command can carry an Android and an iOS build.
What the build must be#
An APK with both arm64-v8a and x86_64 native code, or an iOS Simulator .app, zipped. For Expo and React Native, a release build with the JavaScript bundled in. The guides: Android, iOS, and skipping unchanged builds with a fingerprint.
This post is part of Mobile release testing: a guide for app teams.
Filed underiPhone and iPadAndroidApp builds and reviewCI, schedules and agents