T3 Code Mobile

Quickstart

This app has three variants:

• development: Expo dev client, installable side-by-side as T3 Code Dev
• preview: persistent internal preview build, installable side-by-side as T3 Code Preview
• production: store/release build as T3 Code

Run commands from apps/mobile.

T3 Connect is optional and disabled in a fresh clone. Public configuration belongs in the repository-root .env or .env.local, not an apps/mobile/.env file. See ../../.env.example.

Development

Start Metro for the dev client:

Build and run the local iOS dev client:

If your Xcode account only has a Personal Team, use a bundle identifier you control and opt into the reduced-capability local build. Personal Team builds omit the widget and share extensions, push entitlement, and native Sign in with Apple entitlement; builds without this opt-in are unchanged.

Build and install a self-contained Release app that does not need Metro:

The Personal Team equivalent also needs a unique bundle identifier:

Build and run the local iOS preview app:

Force the review diff highlighter engine:

javascript is the default and recommended setting for the review diff screen. Set EXPO_PUBLIC_REVIEW_HIGHLIGHTER_ENGINE=native only when you explicitly want to test the native Shiki engine.

Inspect the resolved Expo config for a variant:

Run static checks for mobile native code:

The native lint task runs SwiftLint for Swift plus ktlint and detekt for Kotlin. Missing native tools are reported as warnings and skipped locally. CI installs the default toolset from apps/mobile/Brewfile before running the native checks.

EAS Builds

CI uses Expo fingerprinting with the preview:dev profile to reuse an existing compatible build when possible, or start a new internal EAS build when native runtime inputs change. Production and default local builds continue to use the appVersion runtime policy.

For preview or production EAS environments, set T3CODE_CLERK_PUBLISHABLE_KEY, T3CODE_CLERK_JWT_TEMPLATE, and T3CODE_RELAY_URL as EAS environment variables. Expo config maps the canonical values into the mobile build.

Create a PR preview dev-client build manually:

Create a cloud dev-client build:

Create a persistent preview build:

Android equivalents: