Frequently asked questions

Three things: an Apple Developer account, at least one project with Xcode Cloud configured, and an App Store Connect API key. Andon walks you through creating the key on first launch — where to click, which role to pick — in about two minutes.

The Developer role is enough to browse builds, read logs, start builds, and toggle workflows. TestFlight features (beta groups, distribution, feedback) require the App Manager role. Andon detects what your key can do and adapts — features your key can’t reach are clearly disabled, not hidden.

No — and no third-party app can. Connecting a repository and creating an Xcode Cloud product isn’t exposed by Apple’s API; you do that once in Xcode or on the App Store Connect website. Once a product exists, Andon covers day-to-day life with your builds.

Andon runs on iPhone and iPad, and requires iOS 26 / iPadOS 26 or later.

Yes. Your key is stored in the device Keychain, marked “this device only”, and is used solely to sign requests sent directly to Apple’s App Store Connect API over HTTPS. There is no Andon server, so your key cannot be sent to one. See the privacy policy for the full picture.

No. No analytics, no trackers, no crash-reporting SDK, no account. Build data fetched from Apple is cached on your device so the app works offline, and you can wipe that cache from Settings at any time.

Not yet. Notifying you reliably when a build finishes requires a push relay server — background polling alone cannot guarantee it (iOS decides when an app gets to check on its builds), and we chose to ship nothing rather than something that only works sometimes.

Push notifications are on the roadmap as a strictly opt-in service, and it will never see your API key. In the meantime, the app, its widgets, and its Shortcuts always show the latest state whenever you look.

Apple’s API doesn’t stream logs for a build in progress. Andon shows per-action progress while a build runs, then the complete logs, issues, test results, and artifacts as soon as it finishes.

Andon polls adaptively — every few seconds when a build is running on screen, more calmly otherwise — while respecting Apple’s API rate limits. Rather than simulating real time, Andon shows exactly what Apple’s API last returned: nothing is interpolated or guessed.

Not from Andon — Apple’s API has no endpoint to cancel a build, so no third-party app can. Canceling remains available in Xcode and on the App Store Connect website.

Yes. Andon can create, duplicate, edit, and delete workflows: name and description, every start condition (branch, tag, pull request, scheduled, and the manual variants — patterns, file rules, auto-cancel included), the build, analyze, test, and archive actions, the Xcode and macOS versions, clean builds, and edit restrictions — everything Apple’s App Store Connect API exposes.

Two corners the API keeps to itself: the test destinations of a test action are preserved exactly as configured but picked in Xcode, and the next two answers cover the rest.

Deployment post-actions — the step that automatically pushes a fresh build to TestFlight testers — aren’t exposed by Apple’s API: Andon shows them in a build’s results, but no third-party app can configure them. Set them up in Xcode or on the App Store Connect website.

You can also do without them: once a build lands in TestFlight, Andon distributes it to any beta group in a couple of taps — release notes and beta review included.

In Xcode and on the App Store Connect website only. Apple’s API doesn’t expose environment variables at all — not even for reading. The upside: your secrets never transit through anything but Apple’s own tools, Andon included.

Andon is a paid app: one purchase, no subscription, no in-app purchases in v1.

Version 1 supports one API key at a time — one key already covers every app of a team. Multi-account support is under consideration for a future release.