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.
TypeScript 3d-modelingagent-frameworkagent-harnessai-agentscadclaude-codecodexcoding-agentsdeveloper-toolsesp32game-developmentmcp-servermulti-agentopen-hardwareopencodeopenharnesspcbroboticsterminaltmux
task(mobile): sign TestFlight builds without a dev certificate
tony63631be12c78
diff --git a/mobile/RELEASE.md b/mobile/RELEASE.mdindex e4f14a10e..c42c6d9bd 100644--- a/mobile/RELEASE.md+++ b/mobile/RELEASE.md@@ -23,9 +23,19 @@ One command. Credentials are already on the release Mac, so there is nothing to```bashbash mobile/scripts/release-ios.sh # build -> validate -> uploadbash 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+bash mobile/scripts/release-ios.sh --skip-build # upload what the last build left in build/ios```+The build is `flutter build ios --config-only` followed by `xcodebuild archive` and+`-exportArchive`, not `flutter build ipa`: Flutter cannot hand xcodebuild an API key, so on a Mac with+no signing certificate and no Xcode account it failed at signing whatever key was configured.++The archive is **unsigned**; the export signs the app and its frameworks with the team's Apple+Distribution certificate. Signing the archive would need an Apple Development certificate on the Mac,+and the shared release account (`[email protected]`) has used up its quota of those — Xcode+answers "Choose a certificate to revoke", and revoking one breaks whichever Mac holds it. Runner has+no entitlements file, so the export's own entitlements are all the app needs.+### Where the credentials live, and why not here```@@ -40,30 +50,27 @@ App Store Connect session — the repo's own `.gitignore` already refuses `*.p8`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.+▸ App Store Connect API (role **Admin**), drop the one-time `.p8` download into+`~/.appstoreconnect/private_keys/`, and write the two ids into the `.env` above. That is the whole+setup: the script hands the same key to the export, which signs with the team's cloud-managed+distribution certificate — nothing to sign into Xcode, nothing to import into the keychain. An App+Manager key uploads but cannot sign that way. An Apple ID plus an **app-specific** password+(`ASC_USERNAME` / `ASC_APP_PASSWORD`) uploads too, but then signing needs the account in Xcode (below).The script validates before uploading, which is what catches a duplicate build number or a missingicon size in thirty seconds instead of in an email twenty minutes later.### Upload with an existing Xcode account-If the release script stops at `no credentials`, an Apple account already signed into Xcode can-also sign and upload. Select the Autonomous Inc. team, then build the same production archive:--```bash-cd mobile-flutter build ipa --release --export-method app-store-```--Export that archive with `xcodebuild -exportArchive -allowProvisioningUpdates`, using an export-options plist with `method = app-store-connect`, `destination = upload`, `signingStyle = automatic`,-`teamID = 54DJVWMJCC` and `manageAppVersionAndBuildNumber = false`. The archive is-`mobile/build/ios/archive/Runner.xcarchive`. This uses Xcode's account session; it does not configure-API-key credentials for `release-ios.sh`.+With neither credential set, the script signs **and** uploads with the Apple account signed into+Xcode ▸ Settings ▸ Accounts (a member of the Autonomous Inc. team): it archives as above, then runs+`xcodebuild -exportArchive -allowProvisioningUpdates` with `method = app-store-connect`,+`destination = upload`, `signingStyle = automatic`, `teamID = 54DJVWMJCC` and+`manageAppVersionAndBuildNumber = false` on `mobile/build/ios/archive/Runner.xcarchive`. Nothing is+validated first — altool cannot borrow Xcode's session — so `--validate-only` refuses this path, and+a duplicate build number shows up as the upload failing.-Build 49 used this path. Apple accepted the upload and started processing it. Xcode reported a+Build 49 used this path, by hand. Apple accepted the upload and started processing it. Xcode reported anon-blocking missing dSYM for the vendored WebRTC framework; native crashes inside that frameworkmay lack symbolicated stacks until the matching symbols are supplied.diff --git a/mobile/pubspec.yaml b/mobile/pubspec.yamlindex 665889659..da0490211 100644--- a/mobile/pubspec.yaml+++ b/mobile/pubspec.yaml@@ -2,7 +2,7 @@ name: harness_mobiledescription: "Harness viewer for iOS and Android."publish_to: 'none'-version: 1.0.0+51+version: 1.0.1+51environment:sdk: ^3.13.0diff --git a/mobile/scripts/release-ios.sh b/mobile/scripts/release-ios.shindex 3ea3ab9d5..222378542 100755--- a/mobile/scripts/release-ios.sh+++ b/mobile/scripts/release-ios.sh@@ -1,9 +1,9 @@#!/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.).+# This replaces the Xcode Organizer round trip — 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@@ -16,19 +16,26 @@# 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:+# Auth, first one found:# 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.+# not expire on a password change, and it SIGNS too — the export is+# handed the same key, so a Mac with no certificate and no Xcode account+# signs with the team's cloud-managed distribution certificate. That+# needs a key with the Admin role; App Manager can upload but not sign.# 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.+# Uploads only: signing still needs the account in Xcode (below).+# neither the Apple account signed into Xcode ▸ Settings ▸ Accounts signs AND+# uploads (`xcodebuild -exportArchive`, destination upload). Nothing is+# validated first, so --validate-only needs one of the two above.## 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+# bash mobile/scripts/release-ios.sh --skip-build upload what the last build left in build/iosset -euo pipefailROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)" # mobile/@@ -55,6 +62,13 @@ fiecho "==> version $SHORT, build $BUILD"echo " ASC must have a version record called exactly '$SHORT', and must not already hold build $BUILD."+# The export options name the team, so read it from the project rather than repeat it here.+TEAM_ID="$(sed -n 's/.*DEVELOPMENT_TEAM = \([A-Z0-9]*\);.*/\1/p' ios/Runner.xcodeproj/project.pbxproj | head -1)"+if [[ -z "$TEAM_ID" ]]; then+ echo "no DEVELOPMENT_TEAM in ios/Runner.xcodeproj/project.pbxproj" >&2+ exit 1+fi+# -- 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@@ -67,49 +81,152 @@ if [[ -z "${ASC_KEY_ID:-}" && -z "${ASC_USERNAME:-}" && -f "$ASC_CONFIG" ]]; thesource "$ASC_CONFIG"fi-AUTH=()+AUTH=() # altool+XCODE_AUTH=() # xcodebuild; empty means Xcode's own signed-in account+UPLOAD_WITH_XCODE=0if [[ -n "${ASC_KEY_ID:-}" && -n "${ASC_ISSUER_ID:-}" ]]; thenAUTH=(--apiKey "$ASC_KEY_ID" --apiIssuer "$ASC_ISSUER_ID")- echo "==> authenticating with API key $ASC_KEY_ID"+ # altool finds the .p8 by itself; xcodebuild has to be given its path.+ KEY_FILE=""+ for dir in "$HOME/.appstoreconnect/private_keys" "$HOME/.private_keys"; do+ if [[ -f "$dir/AuthKey_$ASC_KEY_ID.p8" ]]; then+ KEY_FILE="$dir/AuthKey_$ASC_KEY_ID.p8"+ break+ fi+ done+ if [[ -z "$KEY_FILE" ]]; then+ echo "API key $ASC_KEY_ID: no AuthKey_$ASC_KEY_ID.p8 in ~/.appstoreconnect/private_keys or ~/.private_keys" >&2+ exit 1+ fi+ XCODE_AUTH=(-authenticationKeyPath "$KEY_FILE" -authenticationKeyID "$ASC_KEY_ID"+ -authenticationKeyIssuerID "$ASC_ISSUER_ID")+ echo "==> signing and uploading with API key $ASC_KEY_ID"elif [[ -n "${ASC_USERNAME:-}" && -n "${ASC_APP_PASSWORD:-}" ]]; thenAUTH=(--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+ echo "==> uploading as $ASC_USERNAME; signing with the account in Xcode ▸ Settings ▸ Accounts"+elif [[ "$VALIDATE_ONLY" == 1 ]]; then+ echo "--validate-only needs ASC_KEY_ID + ASC_ISSUER_ID or ASC_USERNAME + ASC_APP_PASSWORD," >&2+ echo "or put them in $ASC_CONFIG — Xcode's account can upload but not validate on its own." >&2exit 1+else+ UPLOAD_WITH_XCODE=1+ echo "==> no API key or app-specific password: signing AND uploading with the Apple account in"+ echo " Xcode ▸ Settings ▸ Accounts (a member of team $TEAM_ID). Nothing is validated first."fi+ARCHIVE="$ROOT/build/ios/archive/Runner.xcarchive"+IPA_DIR="$ROOT/build/ios/ipa"+WORK="$(mktemp -d)"+trap 'rm -rf "$WORK"' EXIT++# `${XCODE_AUTH[@]+...}`, not `"${XCODE_AUTH[@]}"`: macOS's bash 3.2 calls an empty array unbound+# under `set -u`.+#+# One export for both ways out of the archive: `export` writes the ipa altool validates and uploads,+# `upload` hands the build to ASC from xcodebuild itself, on whatever account signed it.+export_archive() {+ cat > "$WORK/ExportOptions.plist" <<EOF+<?xml version="1.0" encoding="UTF-8"?>+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">+<plist version="1.0">+<dict>+ <key>method</key><string>app-store-connect</string>+ <key>destination</key><string>$1</string>+ <key>signingStyle</key><string>automatic</string>+ <key>teamID</key><string>$TEAM_ID</string>+ <key>manageAppVersionAndBuildNumber</key><false/>+</dict>+</plist>+EOF+ xcodebuild -exportArchive -archivePath "$ARCHIVE" -exportPath "$IPA_DIR" \+ -exportOptionsPlist "$WORK/ExportOptions.plist" \+ -allowProvisioningUpdates ${XCODE_AUTH[@]+"${XCODE_AUTH[@]}"}+}++# 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 artifact itself and say so.+warn_if_stale() { # $1 = short version, $2 = build number, both as read from the artifact+ if [[ -n "$2" && ( "$2" != "$BUILD" || "$1" != "$SHORT" ) ]]; then+ echo "!! this build is $1 ($2), 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+}++uploaded() {+ 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+}+# -- build ----------------------------------------------------------------------------------------+# Not `flutter build ipa`: it cannot pass xcodebuild an API key, so on a Mac with no certificate and+# no Xcode account it fails at signing whatever key is configured. `--config-only` does Flutter's+# part (Generated.xcconfig from pubspec.yaml, pods) and xcodebuild does the rest, as on Xcode Cloud.+#+# The archive is left UNSIGNED and the export signs it, app and frameworks alike, with the team's+# Apple Distribution certificate. A signed archive would need an Apple Development certificate on+# this Mac first, and the shared release account has used up its quota of those ("Choose a+# certificate to revoke") — revoking one breaks whichever Mac holds it. Runner has no entitlements+# file, so the export's own (application-identifier, team, beta-reports-active) are all it needs.if [[ "$SKIP_BUILD" == 0 ]]; then- echo "==> flutter build ipa"- flutter build ipa --release --export-method app-store+ echo "==> flutter build ios --config-only"+ flutter build ios --release --config-only++ echo "==> xcodebuild archive (unsigned)"+ xcodebuild -workspace ios/Runner.xcworkspace -scheme Runner -configuration Release \+ -sdk iphoneos -destination generic/platform=iOS -archivePath "$ARCHIVE" \+ -quiet archive COMPILER_INDEX_STORE_ENABLE=NO \+ CODE_SIGNING_ALLOWED=NO CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY=""++ if [[ "$UPLOAD_WITH_XCODE" == 0 ]]; then+ echo "==> xcodebuild -exportArchive"+ export_archive export+ fi+fi++# -- Xcode's account: upload straight from the archive --------------------------------------------+if [[ "$UPLOAD_WITH_XCODE" == 1 ]]; then+ if [[ ! -f "$ARCHIVE/Info.plist" ]]; then+ echo "no archive at $ARCHIVE — run without --skip-build" >&2+ exit 1+ fi+ echo "==> $ARCHIVE"+ warn_if_stale \+ "$(plutil -extract ApplicationProperties.CFBundleShortVersionString raw -o - "$ARCHIVE/Info.plist" 2>/dev/null || true)" \+ "$(plutil -extract ApplicationProperties.CFBundleVersion raw -o - "$ARCHIVE/Info.plist" 2>/dev/null || true)"++ echo "==> uploading with Xcode's account"+ export_archive upload+ uploaded+ exit 0fi-IPA="$(ls -t build/ios/ipa/*.ipa 2>/dev/null | head -1 || true)"+# -- API key or app-specific password: validate, then upload the ipa ------------------------------+IPA="$(ls -t "$IPA_DIR"/*.ipa 2>/dev/null | head -1 || true)"if [[ -z "$IPA" ]]; thenecho "no .ipa in build/ios/ipa — run without --skip-build" >&2exit 1fiecho "==> $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+warn_if_stale "$(ipa_key CFBundleShortVersionString)" "$(ipa_key CFBundleVersion)"-# -- 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"@@ -122,17 +239,4 @@ fiecho "==> 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+uploaded