• SPEEDFLIGHT_SECRET

  is the upload key. You mint it once per repo and keep it in

  .env.speedflight

  (gitignored). It is the user's, for this app. Do not share it, print it, or commit it.
• The page id is derived on the server:

  sha256("<bundleId>\n<secret>")

  , first 32 hex chars. That is what the share URL contains. Whoever has the link can install and download. They cannot upload.

• First run in a repo (no

  .env.speedflight

  , or no

  scripts/speedflight.sh

  ): do Setup, then Share a build.
• Every later run: Share a build.
• If the user asks for it to run without a Mac, or from a Linux devbox or sandbox: On request: run it in GitHub Actions.

rg -n "CFBundleURLSchemes" -A3 --glob '*.plist' --glob 'project.yml' --glob '*.pbxproj'

tressa://

• XcodeGen (

  project.yml

  ), under the app target:
  yaml

  info:
    properties:
      CFBundleURLTypes:
        - CFBundleURLName: com.example.app
          CFBundleURLSchemes: [tressa]

• Plain Xcode: add

  CFBundleURLTypes

  to the target's

  Info.plist

  .

.env.speedflight

SPEEDFLIGHT_DEEP_LINK=tressa://

shellcheck disable=SC1091

• (if $repoUrl == "" then {} else {repoUrl:$repoUrl} end)')" create() { curl -sfS --retry 3 --retry-all-errors --retry-delay 3
  -X POST "$1/api/apps/$SPEEDFLIGHT_SECRET/$BUNDLE_ID/builds"
  -H "Content-Type: application/json" --data "$META" } CREATED="$(create "$BASE" || create "$FALLBACK_BASE")" BUILD_ID="$(jq -r .buildId <<<"$CREATED")" PAGE_URL="$(jq -r .pageUrl <<<"$CREATED")"

1. Commit and push first. The page shows the branch and commit, and the script refuses a dirty or unpushed tree. If the user's work is not committed, commit it with a real message and push. Ask before pushing to a branch that is not the user's own feature branch.
2. Write the title and notes. Look at the diff since the last shared build (

   git log

   , or the last Build page link in the conversation). The title is one line, what this build is. The notes say what changed and what to test, written for the person holding the phone. Plain text, a few short lines, no markdown headers.
3. Screenshots (optional, encouraged). The page shows them like the App Store, but they are not marketing. They show what changed: the screens you touched, before and after if that helps. Use what you have: screenshots the user gave you, or ones you took while testing on the simulator (

   xcrun simctl io booted screenshot 01-paywall.png

   ). Do not start a simulator build just to get them. Any mix of iPhone and iPad, portrait and landscape, lays out fine; the page sets one height. PNG, JPG, or WebP, under 10MB each, at most 12.
4. Run the script.
   bash

   scripts/speedflight.sh "Onboarding paywall rewrite" "$(cat <<'EOF'
   What changed
   - New onboarding paywall with the annual plan first
   - Fixed the crash when restoring purchases offline
   
   What to test
   - Fresh install, go through onboarding, tap Restore with Wi-Fi off
   - Check the paywall shows 3 plans and the annual one is selected
   EOF
   )" shots/paywall.png shots/restore.png

   Screenshot paths come after the notes, in the order they should show. It takes 2 to 5 minutes. The last line is

   Build page: <url>

   .
5. Post the link in the chat. Every run, always, as a plain URL on its own line so it is tappable. The link is the app page, the

   Build page:

   line the script prints:

   https://speedflight.dev/a/<pageId>

   . Never share a URL with a build id after it (

   /a/<pageId>/<buildId>

   ); that is one build's install page, and the user wants the page with all of them. Say what is on it: the title, version and build number, and that Install works from Safari on a registered iPhone. Do not paste the link anywhere public. Do not print the secret.

• "No Accounts" or "No profiles": the ASC key does not belong to

  TEAM_ID

  , or lacks the App Manager role.
• "Could not read Info.plist" or "bundle id is X, but this page is for Y": the scheme built a different target than

  BUNDLE_ID

  . Fix the script's facts.
• "working tree is dirty" or "HEAD is not pushed": go back to step 1. Screenshots do not need to be committed; keep them out of git if they are throwaway.
• Upload timeouts: the script retries and falls back to the workers.dev host on its own. Run it again if both fail.

.github/workflows/speedflight.yml

name: Speedflight

on:
  workflow_dispatch:
    inputs:
      title:
        description: One line, what this build is
        required: true
      notes:
        description: What changed and what to test
        required: true
  push:
    branches: ["**"]

concurrency:
  group: speedflight-${{ github.ref }}
  cancel-in-progress: true

jobs:
  build:
    runs-on: macos-latest
    timeout-minutes: 45
    env:
      ASC_KEY_ID: ${{ secrets.ASC_KEY_ID }}
      ASC_ISSUER_ID: ${{ secrets.ASC_ISSUER_ID }}
      SPEEDFLIGHT_SECRET: ${{ secrets.SPEEDFLIGHT_SECRET }}
      SPEEDFLIGHT_DEEP_LINK: ${{ vars.SPEEDFLIGHT_DEEP_LINK }}
      SPEEDFLIGHT_AUTHOR: ${{ github.actor }}
    steps:
      - uses: actions/checkout@v4
      - name: Install the ASC key
        run: |
          mkdir -p ~/private_keys
          printf '%s' "${{ secrets.ASC_PRIVATE_KEY }}" > ~/private_keys/AuthKey_${ASC_KEY_ID}.p8
      # Only for XcodeGen projects.
      - run: brew install xcodegen
      - name: Cut and share
        run: |
          TITLE="${{ inputs.title }}"
          NOTES="${{ inputs.notes }}"
          # On push, the commit message is the title and its body the notes.
          [ -n "$TITLE" ] || TITLE="$(git log -1 --format=%s)"
          [ -n "$NOTES" ] || NOTES="$(git log -1 --format=%b)"
          [ -n "$NOTES" ] || NOTES="$TITLE"
          scripts/speedflight.sh "$TITLE" "$NOTES" | tee build.log
          grep '^Build page:' build.log >> "$GITHUB_STEP_SUMMARY"

• The page link grants installs. On a public repo, drop the step summary line; anyone can read it. The secret never prints.
• A fresh runner has no Apple Development certificate, so cloud signing mints one per run, and Apple caps those. After roughly ten runs the archive fails with "reached the maximum number of certificates". The fix is one fixed identity imported from a

  .p12

  secret before the archive step; ask the user for it when that error appears, and never create or revoke certificates yourself.
• Screenshots in CI need a simulator run in the workflow. Skip them unless the user asks; the page works without.
• Tell the user to keep pushing normally. Every push to any branch cuts a build; narrow

  branches:

  if that is too much.