0Pricing
React Native Academy · 课时

使用 EAS Build 配置签名

使用生产构建配置文件设置 eas.json，运行 eas credentials 管理证书，并触发 EAS Build 生成已签名的 .ipa 文件。

使用 EAS Build 配置签名 是 CoddyKit 上的免费 React Native Academy 课时。 这是第 2 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 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 init

The 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: XXXXXXXXX

Environment 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 testers

Troubleshooting 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 > Identifiers

Quick 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 配置签名」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 React Native Academy 课程的其余内容，请升级到 CoddyKit PRO。 React Native Academy 课程共包含 4 节课。

「使用 EAS Build 配置签名」这节课中我会学到什么？

使用生产构建配置文件设置 eas.json，运行 eas credentials 管理证书，并触发 EAS Build 生成已签名的 .ipa 文件。 你通过在浏览器中直接运行的动手代码来练习 React Native Academy，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 React Native Academy 需要有经验吗？

无需任何先前经验。CoddyKit 上的 React Native Academy 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 2 节课，共 4 节。

「使用 EAS Build 配置签名」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 React Native Academy 课中编写并运行代码吗？

能。每节 React Native Academy 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

  1. Apple 开发者账户设置与证书
  2. 使用 EAS Build 配置签名
  3. 在 App Store Connect 中准备 App Store 元数据
  4. 提交审核与回应拒绝
← 返回 React Native Academy