Apple IAP元数据API变更：RevenueCat用户无需操作
Apple’s metadata API changes: no action needed with RevenueCat
SaaS订阅产品的开发者必读，明确告知无需改动代码或配置即可规避Apple API废弃风险，节省排查成本。
Apple recently emailed developers about changes to the App Store Connect API, warning that deprecated In-App Purchase and subscription endpoints will begin to be removed in early 2027. If you received that email and use RevenueCat, here’s what it means for your app.
Apple 最近通过电子邮件向开发者通报了 App Store Connect API 的变更，警告称已弃用的应用内购买和订阅端点将于 2027 年初开始被移除。如果你收到了那封邮件并使用 RevenueCat，以下是这对你的应用意味着什么。
First of all, you don’t need to update your RevenueCat SDK or change your configuration because of Apple’s In-App Purchase metadata API changes. Your purchases, renewals, restores, entitlements, webhooks, and product sync are unaffected.
首先，你无需因 Apple 的应用内购买元数据 API 变更而更新 RevenueCat SDK 或更改配置。你的购买、续订、恢复、权益、Webhook 和产品同步均不受影响。
RevenueCat uses the affected App Store Connect endpoints in our product editing tools, but we’re migrating those tools to Apple’s replacements and will complete the migration before Apple removes the deprecated endpoints.
RevenueCat 在我们的产品编辑工具中使用了受影响的 App Store Connect 端点，但我们正在将这些工具迁移至 Apple 的替代方案，并将在 Apple 移除已弃用端点之前完成迁移。
What Apple is changing
Apple 正在进行的变更
App Store Connect API 4.4.1 introduced a version-based workflow for In-App Purchase, subscription, and subscription group metadata. Previously, localizations and images were attached directly to an In-App Purchase, subscription, or subscription group. To change them, you updated the metadata on that product.
App Store Connect API 4.4.1 为应用内购买、订阅和订阅组元数据引入了基于版本的流程。此前，本地化内容和图像直接附加到某个应用内购买、订阅或订阅组上。要更改它们，你需要更新该产品上的元数据。
With the new workflow, localizations and images belong to a version: a container for metadata that goes through App Review. You create a new version when making changes, keeping the proposed updates separate from the metadata already live on the App Store.
在新的流程中，本地化内容和图像属于某个版本：即一个用于存放将通过 App Review（应用审核）的元数据的容器。当你进行更改时，会创建一个新版本，使拟议的更新与应用商店上已上线的元数据保持分离。
Existing integrations can still use the deprecated endpoints during the transition. Apple’s migration guide explains the replacement workflow.
在过渡期间，现有集成仍可使用已弃用的端点。Apple 的迁移指南解释了替代工作流程。
What this means for RevenueCat customers
这对 RevenueCat 客户意味着什么
These changes affect how RevenueCat creates or edits product metadata in App Store Connect through Product Editor and the product tools available through our MCP server.
这些变更影响了 RevenueCat 如何通过 Product Editor（产品编辑器）以及通过我们 MCP 服务器提供的产品工具在 App Store Connect 中创建或编辑产品元数据。
They don’t affect the services your app uses to sell subscriptions and deliver access:
它们不影响你的应用用于销售订阅和交付访问权限的服务：
- Purchase processing and receipt validation
- Renewals and restores
- Entitlements
- Webhooks and integrations
- Product import and sync from App Store Connect
- 购买处理和收据验证
- 续订和恢复
- 权益
- Webhook 和集成
- 从 App Store Connect 导入和同步产品
There’s no minimum RevenueCat SDK version for this migration, and you don’t need to change your RevenueCat configuration.
此次迁移没有最低 RevenueCat SDK 版本要求，也无需更改你的 RevenueCat 配置。
Migration status
迁移状态
We're migrating Product Editor and the MCP product tools to the version-based endpoints. We'll complete the migration before Apple's removal date, and we're targeting December 2026. Until then, these features keep working on the current endpoints, which Apple still supports.
我们正在将 Product Editor 和 MCP 产品工具迁移至基于版本的端点。我们将在 Apple 规定的移除日期之前完成迁移，目标时间为 2026 年 12 月。在此之前，这些功能将继续在当前端点上运行，而 Apple 目前仍支持这些端点。
The new flow has more steps on Apple's side. Products need a draft version, localizations are attached to that version, and the version goes through a review submission. RevenueCat will handle all of that for you. You'll keep using Product Editor the same way.
新流程在苹果端增加了更多步骤。产品需要创建草稿版本，本地化内容绑定到该版本上，然后版本进入审核提交阶段。RevenueCat 将为您处理所有这些操作。您将继续以相同方式使用 Product Editor。
FAQ
常见问题解答
Has RevenueCat migrated off the affected endpoints?
RevenueCat 是否已迁移出受影响的端点？
Not yet. We use them only in Product Editor and the MCP product tools, and the migration is in progress.
尚未完成。我们仅在 Product Editor 和 MCP 产品工具中使用这些端点，目前迁移正在进行中。
When will the migration be done?
迁移何时完成？
Before Apple's removal date. We're targeting December 2026
在苹果移除相关端点之前。我们的目标时间是 2026 年 12 月。
Do I need to update the SDK or change any configuration?
我需要更新 SDK 或更改任何配置吗？
No. This change only affects how RevenueCat talks to App Store Connect, and there's no minimum SDK version tied to it.
不需要。此变更仅影响 RevenueCat 与 App Store Connect 的通信方式，且没有与之绑定的最低 SDK 版本要求。
Are purchases, renewals, restores, entitlements, webhooks or product sync affected?
购买、续订、恢复、权限、Webhook 或产品同步是否受到影响？
No. None of these use the affected endpoints.
不会。这些功能均未使用受影响的端点。
Where can I find updates?
在哪里可以获取更新信息？
We'll update this page when the migration is complete.
迁移完成后，我们将更新此页面。
更进一步：量化金融体系
看懂新闻只是起点——沿量化金融路径，把它变成能交付的工程能力