React Native with Expo is one of the most practical stacks for OpenAI Codex: the code is TypeScript, cloud tasks can run type checks, lint and tests on Linux, and Expo's EAS Build service can produce iOS builds without a local Mac. You still need your own Apple and Google developer accounts, careful handling of credentials, and discipline with over-the-air updates so they stay within store rules.
On this page
Codex is at its best on TypeScript codebases with good tests, and an Expo project is exactly that. The JavaScript layer of a React Native app can be type-checked, linted and unit-tested in a Linux container, which is where Codex cloud tasks run. The native build steps, including the iOS build that normally requires a Mac, can be delegated to Expo Application Services (EAS). That combination lets a small team ship to both stores from a repository where most changes arrive as Codex pull requests.
Set up the project so Codex can verify its own work
Create the project with create-expo-app using the TypeScript template and Expo Router for navigation. Add a test runner (Jest with React Native Testing Library is the common choice), ESLint and a strict tsconfig. Then document the commands in AGENTS.md: install, type check (npx tsc --noEmit), lint and test. Codex runs these before it proposes a change, and the type checker alone catches a large share of the mistakes agents make in React Native, such as wrong prop types or missing navigation params.
Also record the rules that keep the build healthy: prefer Expo SDK modules over community packages when both exist, install packages with npx expo install so versions match the SDK, and do not add packages that need custom native code without approval. Custom native code is possible through config plugins and development builds, but each addition increases build and review complexity.
Builds with EAS instead of a local Mac
EAS Build compiles your app on Expo's servers, including on macOS for iOS, and can manage signing credentials for you. Configure profiles in eas.json, typically development, preview and production. Codex can write and maintain this file, but the credentials themselves stay with you: log in to EAS with your own account, let it generate or upload the iOS distribution certificate and Android upload key, and keep the Expo access token in your CI secrets, not in the Codex environment. Check Expo's current pricing and build limits before you depend on the service for frequent builds.
From build to store, step by step
- Accounts: Apple Developer Program (currently USD 99 per year) and a Google Play developer account (currently a one-time USD 25).
- App identity: set
ios.bundleIdentifierandandroid.packagein the app config. They are hard to change after the first release. - Store records: create the app in App Store Connect and in the Play Console.
- Production build: run
eas build --platform all --profile productionfrom CI. - Submit: use
eas submitto upload the iOS build to App Store Connect and the Android bundle to a Play Console testing track. The first Android upload may need to be done manually in the Console. - Test: distribute through TestFlight and Google Play testing tracks, including the closed test that new personal Play accounts currently need (at least 12 testers for 14 days).
- Release: complete listings, privacy labels and the Data safety form, then submit for review.
Over-the-air updates and store rules
EAS Update lets you push JavaScript and asset changes to installed apps without a store review. It is valuable for bug fixes, and it is also where teams get into trouble. Apple's guidelines restrict apps from downloading code that changes features or functionality beyond what was reviewed (see Guideline 2.5.2 and the developer agreement), and Google Play has comparable policies. A practical rule: use OTA updates for fixes and small adjustments, and ship new features, new permissions or anything that changes the app's purpose through a normal store release. Encode that rule in AGENTS.md and in your release process, because an agent will not weigh policy risk unless you ask it to.
Also bind updates to runtime versions correctly so a JavaScript bundle never reaches a binary whose native modules it does not match. Codex can configure the runtime version policy, but test an update on a production build before relying on it.
Common issues in Codex-built Expo apps
We see recurring patterns. Codex sometimes installs a package with plain npm install, producing a version that does not match the Expo SDK and breaks the native build only on EAS. Permissions get declared in the app config without matching purpose strings for iOS. Environment variables for API endpoints end up in the bundle with development values. And screens that work on one simulator size break on small Android phones. A short pre-release checklist covers these; ours is in the App Store submission checklist for Claude Code and Codex projects. If you are still deciding between React Native and another stack, compare it with Claude Code and Flutter.
Getting it over the line
The build can be automated almost entirely; the store relationship cannot. AppSubmitter.io takes over the publishing process for both stores, including listings, screenshots, privacy forms and communication with reviewers, until the app is live. Teams that want to master Codex-based workflows themselves can join the OpenAI Codex workshops by neoOutput. Before launch, also read privacy manifests and Data safety forms for AI-built apps, since Expo apps inherit privacy obligations from every SDK they include.
Frequently asked questions
Do I need a Mac to ship an Expo app to the App Store?
Not necessarily. EAS Build compiles iOS apps on hosted macOS machines and EAS Submit uploads them. A Mac is still useful for debugging native issues and running the iOS simulator.
Can Codex run the app on a device?
Codex cloud tasks cannot drive phones or simulators. They verify code with type checks, lint and tests. Device testing happens through development builds, TestFlight and Play testing tracks.
Are over-the-air updates allowed by Apple?
Updates that fix bugs or make small changes are widely used. Updates that add new features or change the app's purpose should go through review. Check the current guidelines before relying on OTA for larger changes.