Expo EAS + TestFlight

#7iOS App Builds & Release Pipeline

In client work

1. What we use it for: We use Expo Application Services (EAS Build and EAS Submit) and Apple TestFlight to compile, sign, and deliver iPhone app releases in the cloud without depending on a single developer’s machine.

2. Client use case · RiseSyncState: live

Problem

RiseSync had a half-finished, AI-built 90-day coaching iPhone app (Expo SDK 54 / React Native 0.81, originally scaffolded with the Vibecode AI builder by a prior developer) that needed hardening, backend fixes, and repeatable TestFlight builds ahead of its January 2027 launch.

What the tool did

Signed on 2026-10-17, removed the leftover Vibecode SDK (`2c9d863`), configured production environment variables in `eas.json` (`9f1e3f7`), added `App Riser Settings` and `App Reports` tables after the Airtable `Users` table hit its 500-field ceiling, deployed the Fastify API on Railway, and ran EAS builds 7 through 9 into Apple TestFlight.

Result

Added 172 commits in five days, merged Milestone 1 to the client’s main branch on 2026-10-21/22, and submitted TestFlight build 9 on 2026-10-22 at 20:28 ET (not in the public App Store yet).

3. What it costs us or the client

$0/month on Expo EAS Free (up to 30 mobile builds/month; EAS Starter is $19/month) plus $99/year for the client’s Apple Developer Program account (as of 2026-10-22).

4. Setup notes (how it is wired in)

Configured via `eas.json` build profiles connected to the client’s Apple Developer account and App Store Connect API key; `eas build --platform ios` compiles and signs the binary in the cloud and `eas submit` uploads it directly to TestFlight.

5. What broke & how it was handled

The inherited codebase still carried the prior developer’s Vibecode SDK, stale `AGENTS.md` instructions, two historical `.env` commits, and an ngrok token in a branch README, while the Airtable `Users` table hit Airtable’s hard 500-field cap—requiring us to strip Vibecode, split new features into separate Airtable tables, and lock down `eas.json` production env vars before shipping builds 7–9.

6. What we compared it against & why we picked it

Compared against Capacitor iOS/Android shells (which we use on our own web-first `moHelp` app) and local Xcode archive builds, plus a later proposed Supabase data-layer migration. Because RiseSync already had 102 commits on Expo SDK 54, we chose "ship now, rebuild later" with Expo EAS to get Milestone 1 into TestFlight in five days.

7. Last reviewed: 2026-10-228. Video / tutorial: Episode 1 in production: "AI-Built App to TestFlight in 5 Days (Claude Code + RiseSync)"

All stack tools

Three separate steps. Stop after any of them.

Step 1 is a free 15-minute fit call. Step 2 is the AI Staff Assessment, $500, a written assessment you keep. Step 3 is your first hire at a published price, or you take the assessment and stop.

Step 1

Fit call

$0 · 15 min

tell me which job eats your week: the phone, the inbox, marketing or support
I tell you whether an AI hire fits, and whether I am the right person for it
you leave with the first hire I would start with
a slide deck

video call · same week

book it

Step 2

AI Staff Assessment

$500

a 60-minute video call about how your business runs
my written assessment the same day: whether an AI hire would pay for itself, the job I would hand off first, what to settle first, and the fixed price for that first hire
not taken off the build, and no separate quoting call: the assessment names the package at its published price
proposals written before anyone learned your business

paid when you book · not taken off the build

start here

Step 3

Your first hire

fixed price

Front Desk Hire or Brain + First Hire, at the published price
built in 2 to 6 weeks, then 30 days of tuning
or take the assessment and stop there
bench developers you never met

priced in the assessment

see the prices

iOS App Builds & Release PipelineExpo EAS + TestFlight