Configuring Signing with EAS Build
Set up eas.json with a production build profile, run eas credentials to manage certificates, and trigger an EAS Build that produces a signed .ipa file.
Configuring Signing with EAS Build is a free React Native Academy lesson on CoddyKit — lesson 2 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the React Native Academy learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
What Is EAS Build
EAS Build (Expo Application Services Build) is a cloud build service that compiles your React Native or Expo app on Expo's infrastructure, producing a signed .ipa for iOS or .apk/.aab for Android. You do not need Xcode, Android Studio, or a Mac for iOS builds — EAS provides managed macOS machines. It also handles code signing credentials automatically.
Installing and Logging in to EAS CLI
EAS CLI is the command-line tool you use to trigger builds, manage credentials, and submit apps. Install it globally with npm, then log in with your Expo account. You need an Expo account (free) in addition to your Apple Developer account. Once logged in, EAS can communicate with Apple's API on your behalf to manage certificates and provisioning profiles.
# Install EAS CLI globally
npm install -g eas-cli
# Verify installation
eas --version
# Log in with your Expo account
eas login
# Check who you are logged in as
eas whoami
# Link your project (run from project root)
eas initThe eas.json Configuration File
All EAS Build behavior is configured in eas.json at the project root. You define build profiles — named configurations like development, preview, and production. Each profile specifies the distribution type, credentials source, environment variables, and platform-specific settings. Run eas build:configure to generate an initial eas.json automatically.
// eas.json
{
'cli': { 'version': '>= 5.0.0' },
'build': {
'development': {
'developmentClient': true,
'distribution': 'internal',
'ios': { 'simulator': true }
},
'preview': {
'distribution': 'internal'
},
'production': {
'distribution': 'store',
'credentialsSource': 'remote'
}
},
'submit': {
'production': {
'ios': { 'appleId': 'you@example.com' }
}
}
}Setting Up Credentials Automatically
EAS can set up all iOS signing credentials automatically if you grant it access to your Apple Developer account. When you first run eas build --platform ios, EAS prompts you: generate a new certificate and provisioning profile, or use an existing one. Choose the auto-generate option and EAS creates a distribution certificate via the Apple API, generates a matching provisioning profile, and stores both securely in EAS's credential storage.
# Trigger a production iOS build
eas build --platform ios --profile production
# EAS prompts:
# ? Would you like to log in to your Apple account?
# > Yes
# Enter Apple ID: you@example.com
# Enter password: (app-specific password)
#
# ? Generate a new Apple Distribution Certificate?
# > Generate a new certificate <- choose this
#
# ? Generate a new Provisioning Profile?
# > Generate a new profile <- choose this
#
# Build queued...Viewing and Managing Credentials
The eas credentials command opens an interactive menu to view, update, or remove stored credentials. You can see your certificate's expiry date, the provisioning profile type, and which App ID it covers. You can also fetch credentials from the cloud to use locally, or push a locally generated .p12 and .mobileprovision to EAS if you prefer to manage them yourself.
# View all stored credentials
eas credentials
# Select:
# Platform: iOS
# App: com.yourcompany.myapp
#
# EAS shows:
# Distribution Certificate
# - Issued to: Your Name
# - Expires: Dec 15, 2026
# - Serial: A1B2C3...
# Provisioning Profile
# - Type: App Store
# - Expires: Dec 15, 2026
# - Profile UUID: XXXXXXXXXEnvironment Variables in EAS Build
EAS Build supports environment variables for build-time secrets and configuration. Define them in eas.json under the env key for a specific profile, or store sensitive values in EAS Secrets via eas secret:create. EAS Secrets are encrypted and only injected into builds — they are never logged or exposed to the public. Use them for API keys, tokens, or any value that must not be in source control.
// eas.json — environment variables per profile
{
'build': {
'production': {
'distribution': 'store',
'env': {
'EXPO_PUBLIC_API_URL': 'https://api.yourapp.com',
'APP_VARIANT': 'production'
}
},
'preview': {
'env': {
'EXPO_PUBLIC_API_URL': 'https://staging.yourapp.com',
'APP_VARIANT': 'staging'
}
}
}
}
// Add secrets (sensitive values NOT in eas.json)
// eas secret:create --scope project --name STRIPE_SECRET_KEY --value sk_live_...Triggering a Build and Monitoring Progress
Start a production iOS build with eas build --platform ios --profile production. EAS queues the build on a macOS runner and returns a build URL you can monitor in the browser. Build logs stream in real time. The build status progresses through: queued → in progress → finished. A finished build produces a download URL for the .ipa or an automatic TestFlight upload if configured.
# Build and submit to TestFlight in one command
eas build --platform ios --profile production --auto-submit
# Or build first, submit separately
eas build --platform ios --profile production
# View recent builds
eas build:list
# View build logs for a specific build
eas build:view <build-id>Local EAS Builds for Debugging
If a cloud build fails and you cannot diagnose the issue from logs, run a local EAS build with eas build --local. This runs the exact same build process on your Mac using the same steps as the cloud runner. You get full access to intermediate files and can insert debugging steps. Local builds require Xcode installed but use EAS's build orchestration scripts.
# Run the EAS build locally on your Mac
eas build --platform ios --profile production --local
# The build output is placed in:
# ./build-*.ipa (in the project root)
# Useful flags:
# --no-wait (don't stream output, just start)
# --clear-cache (ignore previous build cache)Managed vs Bare Workflow Signing
In the managed workflow (Expo), EAS handles all native signing details — you just configure eas.json. In the bare workflow (ejected React Native), you can still use EAS Build but you manage the native project yourself. EAS still handles credential management and cloud compilation, but you may need to configure the Xcode project's signing settings manually via a config plugin or directly in ios/.
// eas.json — bare workflow needs explicit scheme
{
'build': {
'production': {
'distribution': 'store',
'ios': {
'scheme': 'MyApp', // Xcode scheme name
'buildConfiguration': 'Release'
}
}
}
}Ad Hoc Distribution for QA Testers
Ad Hoc distribution lets you install a build directly on up to 100 specific registered devices without going through the App Store or TestFlight. Register tester device UDIDs in the Developer Portal, create an Ad Hoc provisioning profile, build with distribution: 'internal' in EAS, and share the install link. EAS can also register new device UDIDs for your team via the eas device:create command.
// eas.json — internal/ad-hoc build
{
'build': {
'qa': {
'distribution': 'internal',
'ios': { 'simulator': false }
}
}
}
# Register a tester's device
eas device:create
# Build for QA (generates ad-hoc signed .ipa)
eas build --platform ios --profile qa
# Share the install link from the EAS dashboard with testersTroubleshooting Signing Errors
Common signing failures include: certificate mismatch (the stored cert doesn't match the provisioning profile — fix by regenerating both), expired certificate (renew via eas credentials), missing entitlements (a capability is in the entitlements file but not in the provisioning profile — add the capability in the Developer Portal and regenerate the profile), and wrong bundle ID (double-check ios.bundleIdentifier in app.json matches the App ID exactly).
# Common fix: clear and regenerate credentials
eas credentials --platform ios
# Select: Remove all credentials, then run build again
# Or manually force new certificate:
eas credentials --platform ios
# Select: Update Distribution Certificate
# Check bundle ID mismatch
cat app.json | grep bundleIdentifier
# Should match exactly what's in developer.apple.com > IdentifiersQuick Check
Test your understanding of React Native Mobile Development concepts from this lesson.
Lesson Recap
In this lesson you learned: how to configure eas.json with build profiles for development, preview, and production, how EAS manages iOS certificates and provisioning profiles automatically, and how to use environment variables and EAS Secrets for build-time configuration. You also saw how to trigger builds, run them locally for debugging, and troubleshoot common signing errors. Next up we prepare App Store metadata in App Store Connect.
Frequently asked questions
Is the “Configuring Signing with EAS Build” lesson free?
Yes — the full text of “Configuring Signing with EAS Build” is free to read here on the web, and the React Native Academy course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the React Native Academy course, upgrade to CoddyKit PRO.
What will I learn in “Configuring Signing with EAS Build”?
Set up eas.json with a production build profile, run eas credentials to manage certificates, and trigger an EAS Build that produces a signed .ipa file. You practise React Native Academy with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start React Native Academy?
No prior experience is required. React Native Academy on CoddyKit is structured for beginners through advanced learners; this is — lesson 2 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Configuring Signing with EAS Build” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this React Native Academy lesson?
Yes. Every React Native Academy lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.