EAS Build로 서명 구성하기
프로덕션 빌드 프로필로 eas.json을 설정하고 eas credentials를 실행하여 인증서를 관리하며, 서명된 .ipa 파일을 생성하는 EAS Build를 시작합니다.
EAS Build로 서명 구성하기은(는) CoddyKit의 무료 React Native Academy 강의입니다. 이것은 4개 중 2번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 React Native Academy 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. React Native Academy 강의에는 총 4개의 강의가 포함되어 있습니다.
이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.
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.
자주 묻는 질문
“EAS Build로 서명 구성하기” 강의는 무료인가요?
네 — “EAS Build로 서명 구성하기” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 React Native Academy 강의 전체를 잠금 해제할 수 있습니다. React Native Academy 강의에는 총 4개의 강의가 포함되어 있습니다.
“EAS Build로 서명 구성하기”에서 뭘 배우나요?
프로덕션 빌드 프로필로 eas.json을 설정하고 eas credentials를 실행하여 인증서를 관리하며, 서명된 .ipa 파일을 생성하는 EAS Build를 시작합니다. 브라우저에서 직접 실행하는 실습 코드로 React Native Academy을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.
React Native Academy을(를) 시작하는 데 경험이 필요한가요?
사전 경험은 필요하지 않습니다. CoddyKit의 React Native Academy은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 2번째 강의입니다.
“EAS Build로 서명 구성하기” 강의는 얼마나 걸리나요?
대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.
이 React Native Academy 강의에서 코드를 작성하고 실행할 수 있나요?
네. 모든 React Native Academy 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.
이 강의의 모든 강의
- Apple Developer 계정 설정 및 인증서
- EAS Build로 서명 구성하기
- App Store Connect에서 App Store 메타데이터 준비하기
- 심사 제출 및 거부에 대응하기