Skip to content

The ultimate harness for coding agents and beyond. All your agents. All your machines. One command center. Start with code, then follow your curiosity and build across disciplines: CAD, circuits, robots, games and music.

feat(mobile): update targeted device family and versioning for iOS app release

Dev jacobf7e11359aecf
diff --git a/mobile/RELEASE.md b/mobile/RELEASE.md
new file mode 100644
index 000000000..3dd768a5c
--- /dev/null
+++ b/mobile/RELEASE.md
@@ -0,0 +1,201 @@
+# Releasing the iOS app
+
+The App Store record is **Autonomous Harness** (`ai.autonomous.harness.ios`, team 54DJVWMJCC —
+Autonomous Inc.). Everything below is the iOS side only; the desktop app ships from
+`desktop/RELEASE.md` on its own tags and shares nothing with this.
+
+## The two numbers that decide whether an upload is visible at all
+
+App Store Connect keys a build on the pair `(CFBundleShortVersionString, CFBundleVersion)` — in
+`pubspec.yaml` that is `version: 1.0.0+2`, so `1.0.0` and `2`.
+
+- **Bump the `+N` before every upload.** A pair ASC has already seen is refused, and the refusal
+ arrives *by email* — the ASC UI shows nothing at all, which is exactly what "I uploaded it and
+ nothing happened" looks like.
+- **The short version must match the ASC version record.** A build uploaded as `1.0.0` never appears
+ under a version record called `1.0`: the Build section stays empty and the version cannot be
+ submitted. Rename one so the two strings are identical.
+
+## Upload
+
+One command. Credentials are already on the release Mac, so there is nothing to export:
+
+```bash
+bash mobile/scripts/release-ios.sh # build -> validate -> upload
+bash mobile/scripts/release-ios.sh --validate-only # rehearse, upload nothing
+bash mobile/scripts/release-ios.sh --skip-build # upload the ipa already in build/ios/ipa
+```
+
+### Where the credentials live, and why not here
+
+```
+~/.appstoreconnect/harness-release.env ASC_KEY_ID + ASC_ISSUER_ID (chmod 600)
+~/.appstoreconnect/private_keys/AuthKey_<ASC_KEY_ID>.p8 the private key (chmod 600)
+```
+
+The script sources that `.env` whenever the environment does not already carry the values, so CI can
+still pass them in. **They are deliberately not written into this file.** This repo is public, and a
+Key ID plus an Issuer ID are precisely the two halves a leaked `.p8` would need to become a working
+App Store Connect session — the repo's own `.gitignore` already refuses `*.p8` and `.env*`, and
+putting the other halves in Markdown would walk straight around that.
+
+Setting up a second machine: create a Team Key at App Store Connect ▸ Users and Access ▸ Integrations
+▸ App Store Connect API (role App Manager), drop the one-time `.p8` download into
+`~/.appstoreconnect/private_keys/`, and write the two ids into the `.env` above. An Apple ID plus an
+**app-specific** password (`ASC_USERNAME` / `ASC_APP_PASSWORD`) works too.
+
+The script validates before uploading, which is what catches a duplicate build number or a missing
+icon size in thirty seconds instead of in an email twenty minutes later.
+
+### Already uploaded
+
+| Build | When | Where it went |
+| --- | --- | --- |
+| `1.0.0 (2)` | 2026-09-16 | TestFlight. Universal (iPhone + iPad) — superseded |
+| `1.0.0 (3)` | 2026-09-16 | TestFlight. **iPhone only** |
+| `1.0.0 (4)` | 2026-09-16 | TestFlight. Adds agent/machine search (`feat/mobile-search`) |
+
+`pubspec.yaml` is therefore at `1.0.0+5`: the repo always holds the NEXT build number, so a release
+runs clean without anyone having to remember the last one.
+
+### Why the app is iPhone-only
+
+`TARGETED_DEVICE_FAMILY = 1`. It was `"1,2"` — Flutter's default — and App Store Connect answers a
+universal binary by requiring a 13-inch iPad screenshot set on top of the iPhone one, which is what
+blocked *Add for Review*.
+
+⚠️ The iPad LAYOUT still exists and is still reached by the shortest-side breakpoint in
+`lib/phone/phone_layout.dart` ("an iPad keeps the rail beside its terminals"). Nothing about it was
+deleted; it simply is not shipped to iPad any more. Putting iPad back is one line here plus a 13-inch
+screenshot set — and a new build, since the requirement follows the BUILD selected on the version,
+not the app record.
+
+Uploading is not submitting. Processing takes 5–30 minutes, then the build becomes selectable in the
+version's **Build** section.
+
+## Metadata — what goes in each field
+
+Fill these on *Distribution ▸ iOS App 1.0.0*. Apple will not accept the version while Description,
+Privacy Policy URL, App Privacy, age rating or pricing are blank.
+
+**Subtitle** (30 max)
+
+```
+Your coding agents, anywhere
+```
+
+**Promotional Text** (170 max — editable later without a new build)
+
+```
+Attach to the coding agents already running on your machines. Same panes, same scrollback, end-to-end encrypted — now from your phone.
+```
+
+**Description**
+
+```
+Harness puts the coding agents running on your own computers in your pocket.
+
+Claude Code, Codex, Cursor and a dozen others already run on your Mac or Linux box. Harness keeps
+each one in a live session on the machine it runs on, and this app attaches to those sessions from
+your phone — the same panes, the same scrollback, exactly where you left them.
+
+WHAT YOU CAN DO
+• Read what an agent is doing right now, from anywhere
+• Type back: answer a prompt, approve a step, send a new instruction
+• Send a photo or screenshot straight into a session
+• Switch between machines and between agents in one list
+• Rename, restart or delete an agent without opening your laptop
+
+HOW IT WORKS
+Sessions live on your machine, not in this app and not on a server. Closing the app, losing signal or
+switching devices changes nothing about what the agent is doing — you reattach and the work is where
+it was.
+
+Everything between your phone and your machine is end-to-end encrypted. Where the network allows it
+the connection is peer-to-peer; where it does not, the relay carries ciphertext it cannot read.
+
+WHAT YOU NEED
+• An Autonomous account
+• At least one Mac or Linux machine running the free Harness CLI, paired to that account
+
+Harness for iPhone is a companion to that setup, not a standalone editor or a general-purpose SSH
+client. Without a paired machine there is nothing for it to attach to.
+```
+
+**Keywords** (100 max, commas, no spaces)
+
+```
+terminal,tmux,ssh,claude,codex,cursor,coding,agent,developer,remote,shell,devops,pair,session
+```
+
+**URLs**
+
+| Field | Value |
+| --- | --- |
+| Support URL | `https://www.autonomous.ai/harness` |
+| Marketing URL | `https://www.autonomous.ai/harness` |
+| Privacy Policy URL | **required — use the real Autonomous policy URL; there is none in this repo to copy** |
+
+**What's New** — leave empty for 1.0.0; it is only shown for updates.
+
+## App Privacy
+
+Answer these from what the code actually does, not from habit. The app has **no third-party SDK**:
+analytics go to Autonomous's own `event_tracking` endpoint (`lib/analytics/`), and crash records are
+written to a local `errors.log` and never leave the device (`lib/core/crash_log.dart`).
+
+| Data type | Collected | Linked to the user | Purpose |
+| --- | --- | --- | --- |
+| Contact Info ▸ Email Address | Yes | Yes | App Functionality, Analytics |
+| Identifiers ▸ User ID | Yes | Yes | App Functionality, Analytics |
+| Usage Data ▸ Product Interaction | Yes | Yes | Analytics |
+| Diagnostics | No | — | crash log stays on device |
+
+**Tracking: No.** Nothing here follows a person across other companies' apps or goes to a data
+broker, so the app needs no App Tracking Transparency prompt.
+
+Terminal contents are deliberately outside all of this: `Analytics.track`'s contract forbids message
+text, prompts, terminal output, file contents and absolute paths, and the session bytes themselves
+are end-to-end encrypted.
+
+## App Review notes — the part that gets 1.0 rejected
+
+A reviewer opens this app, signs in, and sees **no machines**, because they have none running the
+CLI. That reads as a broken or incomplete app (Guideline 2.1) and it is the single most likely reason
+this version comes back. So:
+
+1. Create a demo account and put it in **App Review Information ▸ Sign-In Required**.
+2. Leave a real machine online, paired to that account, for the length of the review — a reviewer who
+ can attach to a live agent cannot mistake the app for an empty shell.
+3. Paste notes along these lines:
+
+```
+Harness is a companion app for developer agents running on the user's own computers.
+
+Demo account: <email> / <password>
+A Mac paired to this account is kept online for the review, so the Agents tab will list live
+sessions. Tap one to attach to its terminal, read the output and type into it.
+
+The app does not run any agent itself: it attaches over an end-to-end encrypted channel to sessions
+owned by the user's own machine, which is why an account with no paired machine shows an empty list.
+
+The camera permission is used only when sending a photo into a session (Agents ▸ a session ▸ the
+image button).
+```
+
+## Submitting
+
+1. **Build** section ▸ `+` ▸ pick the build you uploaded.
+2. Fill everything above, plus age rating and *Pricing and Availability*.
+3. **Add for Review** ▸ **Submit for Review**.
+4. Watch for **Pending Developer Release** after approval — approved is not released; that state
+ waits on a button of yours, forever if you let it.
+
+## Open risk — export compliance
+
+`ios/Runner/Info.plist` declares `ITSAppUsesNonExemptEncryption = false`, which auto-answers the
+export question and is right only for an app whose encryption is the OS's own HTTPS. This app
+terminates its own end-to-end encryption (X25519, ChaCha20-Poly1305, a CPace PAKE — `lib/e2ee/`), so
+that answer is very likely wrong. Settle it with whoever owns export compliance before submitting: a
+wrong answer is not a build failure, it is review asking a question and the version standing still
+until someone answers it.
diff --git a/mobile/ios/Runner.xcodeproj/project.pbxproj b/mobile/ios/Runner.xcodeproj/project.pbxproj
index 9b131549c..80c77170f 100644
--- a/mobile/ios/Runner.xcodeproj/project.pbxproj
+++ b/mobile/ios/Runner.xcodeproj/project.pbxproj
@@ -365,7 +365,7 @@
SDKROOT = iphoneos;
STRING_CATALOG_GENERATE_SYMBOLS = YES;
SUPPORTED_PLATFORMS = iphoneos;
- TARGETED_DEVICE_FAMILY = "1,2";
+ TARGETED_DEVICE_FAMILY = 1;
VALIDATE_PRODUCT = YES;
};
name = Profile;
@@ -493,7 +493,7 @@
ONLY_ACTIVE_ARCH = YES;
SDKROOT = iphoneos;
STRING_CATALOG_GENERATE_SYMBOLS = YES;
- TARGETED_DEVICE_FAMILY = "1,2";
+ TARGETED_DEVICE_FAMILY = 1;
};
name = Debug;
};
@@ -547,7 +547,7 @@
SUPPORTED_PLATFORMS = iphoneos;
SWIFT_COMPILATION_MODE = wholemodule;
SWIFT_OPTIMIZATION_LEVEL = "-O";
- TARGETED_DEVICE_FAMILY = "1,2";
+ TARGETED_DEVICE_FAMILY = 1;
VALIDATE_PRODUCT = YES;
};
name = Release;
diff --git a/mobile/ios/Runner/Info.plist b/mobile/ios/Runner/Info.plist
index 739331d12..60b32dda6 100644
--- a/mobile/ios/Runner/Info.plist
+++ b/mobile/ios/Runner/Info.plist
@@ -24,6 +24,15 @@
<string>????</string>
<key>CFBundleVersion</key>
<string>$(FLUTTER_BUILD_NUMBER)</string>
+ <!-- ⚠️ DECISION, NOT A DEFAULT — and it is currently the OPTIMISTIC one.
+ `false` auto-answers App Store Connect's export-compliance question and
+ is right only for an app whose encryption is the OS's own (an HTTPS
+ call). This app is not that: it terminates its own end-to-end
+ encryption — X25519, ChaCha20-Poly1305 and a CPace PAKE, in `lib/e2ee/`
+ — so the honest answer is very likely `true` plus a self-classification
+ report, or an exemption confirmed with whoever owns export compliance.
+ Getting it wrong is not a build error: review asks, and the version
+ sits still until someone answers. -->
<key>ITSAppUsesNonExemptEncryption</key>
<false/>
<key>LSRequiresIPhoneOS</key>
diff --git a/mobile/pubspec.yaml b/mobile/pubspec.yaml
index 05030ce0d..03cb9060c 100644
--- a/mobile/pubspec.yaml
+++ b/mobile/pubspec.yaml
@@ -2,7 +2,7 @@ name: harness_mobile
description: "Harness viewer for iOS and Android."
publish_to: 'none'
-version: 1.0.0+1
+version: 1.0.0+5
environment:
sdk: ^3.13.0
diff --git a/mobile/scripts/release-ios.sh b/mobile/scripts/release-ios.sh
new file mode 100755
index 000000000..3ea3ab9d5
--- /dev/null
+++ b/mobile/scripts/release-ios.sh
@@ -0,0 +1,138 @@
+#!/usr/bin/env bash
+# Build the iOS app and hand it to App Store Connect. `bash mobile/scripts/release-ios.sh`
+#
+# This replaces the Xcode Organizer round trip, which is the only way builds have reached ASC so far
+# — there is no CI path, and nothing in this repo uploads on a tag. Run it from a Mac that can sign
+# for the team in `ios/Runner.xcodeproj` (DEVELOPMENT_TEAM 54DJVWMJCC, Autonomous Inc.).
+#
+# ⚠️ THE BUILD NUMBER IS THE WHOLE GAME. App Store Connect keys a build on
+# (CFBundleShortVersionString, CFBundleVersion) — `1.0.0` and the number after the `+` in
+# pubspec.yaml — and REFUSES a pair it has seen before. The refusal arrives by email, not in the ASC
+# UI, which is why an upload can look like it simply never happened. Bump the `+N` in
+# `mobile/pubspec.yaml` before every upload; this script prints the pair it is about to send and
+# stops if the short version does not look like one ASC would accept.
+#
+# ⚠️ And the short version must MATCH the version record you are filling in on ASC. A build uploaded
+# as `1.0.0` does not appear under a version called `1.0` — the Build section stays empty and the
+# submission cannot be completed. Make the two strings identical.
+#
+# Auth, either one:
+# ASC_KEY_ID + ASC_ISSUER_ID an App Store Connect API key, with the .p8 in one of the private_keys
+# directories altool searches (~/.appstoreconnect/private_keys or
+# ~/.private_keys), named AuthKey_<ASC_KEY_ID>.p8. Preferred: it does
+# not expire on a password change and is what CI would use later.
+# ASC_USERNAME + ASC_APP_PASSWORD
+# an Apple ID and an APP-SPECIFIC password (appleid.apple.com ▸ Sign-In
+# and Security ▸ App-Specific Passwords). Not the account password.
+#
+# Usage:
+# bash mobile/scripts/release-ios.sh build, validate, upload
+# bash mobile/scripts/release-ios.sh --validate-only build and validate, upload nothing
+# bash mobile/scripts/release-ios.sh --skip-build upload the ipa already in build/ios/ipa
+set -euo pipefail
+
+ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)" # mobile/
+cd "$ROOT"
+
+VALIDATE_ONLY=0
+SKIP_BUILD=0
+for arg in "$@"; do
+ case "$arg" in
+ --validate-only) VALIDATE_ONLY=1 ;;
+ --skip-build) SKIP_BUILD=1 ;;
+ *) echo "unknown argument: $arg" >&2; exit 2 ;;
+ esac
+done
+
+# -- what is about to be uploaded ----------------------------------------------------------------
+VERSION="$(sed -n 's/^version: *//p' pubspec.yaml | head -1)"
+SHORT="${VERSION%%+*}"
+BUILD="${VERSION##*+}"
+if [[ -z "$SHORT" || -z "$BUILD" || "$SHORT" == "$VERSION" ]]; then
+ echo "pubspec.yaml needs a version of the form 1.0.0+3 (got '${VERSION:-<none>}')" >&2
+ exit 1
+fi
+echo "==> version $SHORT, build $BUILD"
+echo " ASC must have a version record called exactly '$SHORT', and must not already hold build $BUILD."
+
+# -- credentials, before spending five minutes on a build ----------------------------------------
+# They live OUTSIDE this repo, which is PUBLIC. A Key ID and an Issuer ID are not secrets on their
+# own, but they are exactly the two halves a stray .p8 would need, and the repo's own .gitignore
+# already refuses `*.p8` and `.env*` — committing the other halves into a Markdown file would walk
+# around that. Sourced only when the environment does not already carry them, so CI can still pass
+# them in.
+ASC_CONFIG="${ASC_CONFIG:-$HOME/.appstoreconnect/harness-release.env}"
+if [[ -z "${ASC_KEY_ID:-}" && -z "${ASC_USERNAME:-}" && -f "$ASC_CONFIG" ]]; then
+ # shellcheck source=/dev/null
+ source "$ASC_CONFIG"
+fi
+
+AUTH=()
+if [[ -n "${ASC_KEY_ID:-}" && -n "${ASC_ISSUER_ID:-}" ]]; then
+ AUTH=(--apiKey "$ASC_KEY_ID" --apiIssuer "$ASC_ISSUER_ID")
+ echo "==> authenticating with API key $ASC_KEY_ID"
+elif [[ -n "${ASC_USERNAME:-}" && -n "${ASC_APP_PASSWORD:-}" ]]; then
+ AUTH=(--username "$ASC_USERNAME" --password "@env:ASC_APP_PASSWORD")
+ echo "==> authenticating as $ASC_USERNAME"
+else
+ echo "no credentials: set ASC_KEY_ID + ASC_ISSUER_ID, or ASC_USERNAME + ASC_APP_PASSWORD," >&2
+ echo "or put them in $ASC_CONFIG (which this script sources when they are unset)." >&2
+ echo "see the header of this script for where each value comes from." >&2
+ exit 1
+fi
+
+# -- build ----------------------------------------------------------------------------------------
+if [[ "$SKIP_BUILD" == 0 ]]; then
+ echo "==> flutter build ipa"
+ flutter build ipa --release --export-method app-store
+fi
+
+IPA="$(ls -t build/ios/ipa/*.ipa 2>/dev/null | head -1 || true)"
+if [[ -z "$IPA" ]]; then
+ echo "no .ipa in build/ios/ipa — run without --skip-build" >&2
+ exit 1
+fi
+echo "==> $IPA"
+
+# The pair printed above came from pubspec.yaml, which is what the NEXT build would carry — with
+# --skip-build the artifact on disk can predate a bump, and then the number announced is not the
+# number sent. Ask the archive itself and say so.
+ipa_key() {
+ unzip -p "$IPA" 'Payload/*.app/Info.plist' 2>/dev/null \
+ | plutil -extract "$1" raw -o - - 2>/dev/null || true
+}
+IPA_SHORT="$(ipa_key CFBundleShortVersionString)"
+IPA_BUILD="$(ipa_key CFBundleVersion)"
+if [[ -n "$IPA_BUILD" && ( "$IPA_BUILD" != "$BUILD" || "$IPA_SHORT" != "$SHORT" ) ]]; then
+ echo "!! this ipa is $IPA_SHORT ($IPA_BUILD), NOT the $SHORT ($BUILD) in pubspec.yaml."
+ echo " It was built before the last bump — drop --skip-build to rebuild, or App Store Connect"
+ echo " will refuse it as a duplicate."
+fi
+
+# -- validate, then upload -------------------------------------------------------------------------
+# Validation catches the whole class of rejections that otherwise arrive by email 20 minutes later:
+# a duplicate build number, a missing icon size, an entitlement the profile does not grant.
+echo "==> validating"
+xcrun altool --validate-app -f "$IPA" -t ios "${AUTH[@]}"
+
+if [[ "$VALIDATE_ONLY" == 1 ]]; then
+ echo "==> validate-only: nothing uploaded"
+ exit 0
+fi
+
+echo "==> uploading"
+xcrun altool --upload-app -f "$IPA" -t ios "${AUTH[@]}"
+
+cat <<EOF
+
+Uploaded $SHORT ($BUILD).
+
+It is NOT submitted, and it is not visible yet. App Store Connect processes the build first (5–30
+minutes, occasionally hours), then it becomes selectable:
+
+ 1. appstoreconnect.apple.com -> Autonomous Harness -> Distribution -> iOS App $SHORT
+ 2. Build section -> + -> pick $SHORT ($BUILD)
+ 3. Add for Review -> Submit for Review
+
+See mobile/RELEASE.md for what the rest of that page needs before Apple will take it.
+EOF
diff --git a/mobile/test/terminal_key_bar_test.dart b/mobile/test/terminal_key_bar_test.dart
index adff08e12..13a853782 100644
--- a/mobile/test/terminal_key_bar_test.dart
+++ b/mobile/test/terminal_key_bar_test.dart
@@ -45,18 +45,19 @@ void main() {
await tester.pump();
}
- testWidgets('the keys a software keyboard has no room for reach the pty', (
+ testWidgets('the keys a software keyboard cannot produce reach the pty', (
tester,
) async {
await pumpBar(tester);
await tapKey(tester, 'esc');
await tapKey(tester, 'tab');
+ // CSI Z, built from the modifier — there is no `TerminalKey.shiftTab`.
+ await tapKey(tester, '\u21e7tab');
await tapKey(tester, 'Up');
- await tapKey(tester, '~');
await tapKey(tester, '7');
- expect(outbound, ['\x1b', '\t', '\x1b[A', '~', '7']);
+ expect(outbound, ['\x1b', '\t', '\x1b[Z', '\x1b[A', '7']);
});
testWidgets('ctrl is handed to the session, which owns the modifier', (