EAS 更新

EAS 更新的规则之一是你需要遵守你所开发的平台和应用商店的规定。这意味着你的更新需要遵循 App Store 和 Play 商店的指南，包括更新内容以及你如何使用它们。这通常意味着对应用行为的更改需要经过审核。

🌐 One of the rules of EAS Update is that you need to follow the rules of the platforms and app stores you are building for. This means your updates need to follow the App Store and Play Store guidelines, including the content of the updates and how you use them. This usually means changes to your app's behavior need to be reviewed.

App Store 的规则经常变化，就像如果你在不使用 Expo 的情况下开发应用一样需要遵守这些规则一样，使用 Expo 和 EAS Update 时也需要遵守这些规则。

🌐 App Store rules regularly change and just as you need to follow them if you were writing an app without Expo, you need to follow them when you are using Expo and EAS Update.

EAS 更新是快速将改进推送给使用你应用的用户的好方法。例如，假设一个应用存在一个需要修复的关键漏洞。使用 EAS 更新，你可以迅速发布修复，并随后提交一个包含修复的新版本。

🌐 EAS Update is a great way to quickly deliver improvements to the people who use your apps. For example, consider an app that has a critical bug that needs to be fixed. With EAS Update, you can quickly get the fix out and later follow up with a new submission that includes the fix built in.

信息 注意：1 个每月活跃用户等于在计费周期内至少下载过 1 次更新的一个应用唯一安装。

• 在结算周期的每一天下载新更新的应用安装计为 1 个月活跃用户。
• 在结算周期内未下载任何新更新的应用安装计为 0 个月活跃用户。
• 卸载并重新安装应用（并在你的结算周期内下载每个应用的更新）算作 2 个月活跃用户。
• 单个设备有两个由单个 Expo 账户拥有的应用，这两个应用都使用更新，则被视为该账户的 2 个月度活跃用户。

默认情况下，expo-updates 会在每次加载应用时检查更新。你可以使用 Updates API 和 应用配置 实现自定义的更新策略。

🌐 By default, expo-updates checks for updates every time the app is loaded. You can implement a custom update strategy with the Updates API and app config.

是的。EAS 更新适用于使用 Continuous Native Generation (CNG) 的项目，也适用于已安装 expo-updates 库的 现有 React Native 项目。

🌐 Yes. EAS Update works with both projects that use Continuous Native Generation (CNG) and existing React Native projects that have the expo-updates library installed.

不。更新会在应用内下载，并根据你的配置进行应用。应用用户将在下次启动或重新加载应用时看到新版本。

🌐 No. Updates are downloaded inside the app and applied based on your configuration. App users see the new version on their next app launch or reload.

EAS 更新使用 运行时版本策略 来确保更新只发送到与原生代码兼容的构建。如果你的原生代码发生更改，则需要创建新的运行时版本。

🌐 EAS Update uses runtime version policies to ensure updates are only sent to builds with compatible native code. If your native code changes, you create a new runtime version.

是的。EAS Update 可与 EAS Workflows 一起使用。你仍然需要为 Android 或 iOS 配置并创建一个新的构建。之后，你可以将更新任务添加到你的工作流配置中。例如：

🌐 Yes. EAS Update works with EAS Workflows. You still need to configure and create a new build for Android or iOS. After that, you can add an update job to your workflow configuration. For example:

jobs:
  publish_update:
    type: update
    params:
      message: 'Fix login button alignment'
      channel: production

有关更多信息，请参见 EAS 工作流程预打包作业。

🌐 For more information, see EAS Workflows pre-packaged jobs.

要使用 GitHub Actions 自动发布更新，请参阅 GitHub PR 预览操作 指南。

🌐 To automate publishing updates with GitHub Actions, see the GitHub Action for PR previews guide.

EAS 更新是一个原生解决方案，同时也可以与 EAS Build 集成，并提供统一的工作流程。CodePush 使用略有不同的方法。要了解 EAS 更新与 CodePush 之间的区别，请参阅 CodePush 与 EAS 更新的概念性差异。

🌐 EAS Update is a native solution that also integrates with EAS Build and provides a unified workflow. CodePush uses a slightly different approach. To learn more about the differences between EAS Update and CodePush, see Conceptual differences between CodePush and EAS Update.

经典更新服务在 2021 年 12 月之前可用，现在已被弃用。不能通过 expo publish 发布新更新，但现有应用将继续接收已经发布并正在使用的经典更新。

🌐 The Classic Updates service was available before December 2021 and is now deprecated. New updates cannot be published via expo publish, however, existing apps will continue to receive Classic Updates that have already been published and are actively used.

我们建议过渡到 EAS Update 或使用 自建更新服务。

🌐 We recommend transitioning to EAS Update or using a self-hosted update service.