11 Failures Before My CI/CD Pipeline Worked: A VibeCoder's Guide to Expo + GitHub Actions + DeployGate

I can't write code. That's not quite right. I describe what I want, Claude writes the code, and I focus on what to build. I'm what people call a VibeCoder — someone who builds products with AI, spending their time on product decisions rather than syntax. I'm building "Arc," a mobile CRM for bodywork therapists, using Expo, React Native, and Supabase. The MVP is 85% done — 28 files, 27 screens, 18 of them functional. The problem wasn't building it. The problem was getting it onto a tester's phone . The last mile is the hardest mile Writing code is fast. Tell Claude "build this screen" and something functional appears in minutes. But putting that build on a tester's iPhone requires: Building with Xcode Generating an .ipa file Uploading it somewhere Telling testers "there's a new version" For a VibeCoder, this "last mile" is the biggest bottleneck — not writing code, but delivering what you've written. TestFlight? Apple's review queue adds hours or days. Expo Go? Can't use native modules.