Android 开发者验证
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
Android 开发者验证是一项新要求,旨在将现实世界中的实体(个人和组织)与其 Android 应用相关联。从 2026 年开始,Android 将要求所有应用都必须由经过验证的开发者进行注册,用户才能在已获认证的 Android 设备上安装。本指南将介绍您需要执行的操作。
为何要做出这些更改
Android 的开发者验证功能可提供额外安全保障。这有助于震慑作恶方,使他们难以散播有害内容,从而保护用户。
此功能有何帮助
更安全、更值得信赖的生态系统有利于整个开发者社区。
- 震慑喜欢匿名操作的不法分子。
- 通过将不良应用与其开发者相关联,更难传播有害内容。
这有助于我们追究开发者的责任、强制执行安全政策,以及移除恶意广告资源网。
- 提高用户信心,帮助您与新用户建立关系并赢得信任。
您需要采取的行动
完成以下两个步骤:
- 验证您的身份:提供信息和文件,以确认您是个人还是组织。
- 注册软件包名称:证明您对应用的所有权,并使用经过验证的身份注册应用。
本指南将逐步介绍每项要求。
时间表和里程碑
Android 开发者验证分阶段推出。这种方法有助于我们根据您的反馈意见进行调整,并让您有时间做好准备。以下是每个阶段的重点:
日期 |
里程碑 |
开发者重点 |
2025 年 8 月 |
宣布新的 Android 开发者验证要求 |
了解新要求并报名参与抢先体验。 |
2025 年 10 月 |
抢先体验开始 |
如果您收到邀请,请开始进行身份验证和应用注册。 |
2026 年 3 月 |
面向所有开发者开放注册 |
开始进行身份验证和应用注册,以便您希望继续在已获认证的 Android 设备上安装的所有应用都能通过验证。 |
2026 年 9 月 |
区域性强制执行开始 |
请验证合规性,以免您的应用在巴西、印度尼西亚、新加坡和泰国境内被禁止安装。 |
2027 年及以后 |
全球强制执行 |
我们正在全球范围内陆续推出此版本。 |
主要概念
在开始之前,请查看以下关键术语:
- 身份验证:提供信息和官方文件来验证您作为个人或组织的身份的过程。
- 软件包名称注册:在应用的唯一软件包名称与签名密钥之间建立正式的可验证关联的过程。
- 应用签名密钥:用于为您的 APK 签名的证书。
- 已获得认证的 Android 设备:Google 会在这些设备上强制执行 Android 开发者验证要求。如果您的应用在已认证的设备上运行,则无论应用的下载来源如何,您都必须遵守这些要求。
- Android 开发者管理中心 (ADC):适用于仅在 Google Play 之外分发应用的开发者。
- Google Play 管理中心 (PDC):供在 Google Play 上分发应用的开发者使用的管理中心。如果您有 Play 管理中心账号,请使用该账号完成验证要求。
寻找您的路径
请使用下表查找适合您情况的控制台和说明。
注册即可抢先体验 Android 开发者验证流程。您可能会收到仅限受邀者使用的抢先体验版的邀请。 |
本页面上的内容和代码示例受内容许可部分所述许可的限制。Java 和 OpenJDK 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-09-10。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["没有我需要的信息","missingTheInformationINeed","thumb-down"],["太复杂/步骤太多","tooComplicatedTooManySteps","thumb-down"],["内容需要更新","outOfDate","thumb-down"],["翻译问题","translationIssue","thumb-down"],["示例/代码问题","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-10。"],[],[],null,["# Android developer verification is a new requirement designed to link real-world\nentities (individuals and organizations) with their Android applications.\nStarting in 2026, Android will require all apps to be registered by verified\ndevelopers in order to be installed by users on certified\n[Android devices](https://www.android.com/certified/partners/). This guide shows what you need to do.\n\nWhy these changes are happening\n-------------------------------\n\nAndroid's developer verification adds a layer of security. This protects users\nby deterring bad actors and making it harder for them to spread harm.\n\nHow this helps you\n------------------\n\nA safer, more trusted ecosystem benefits the entire developer community.\n\n- **Deters bad actors** who prefer to operate anonymously.\n- **Makes it harder to spread harm** by linking bad apps to their developers. This helps us hold developers accountable, enforce safety policies, and remove malicious networks.\n- **Boosts user confidence**, helping you build relationships with new users and establish trust.\n\nWhat you need to do\n-------------------\n\nComplete these two steps:\n\n1. **Verify your identity**: Provide information and documentation to confirm your identity as an individual or an organization.\n2. **Register your package names**: Prove ownership of your apps and register them with your verified identity.\n\nThis guide walks you through each requirement.\n\nTimelines and milestones\n------------------------\n\nThe Android developer verification rollout happens in phases. This approach\nallows us to incorporate your feedback and gives you time to prepare. Here's\nwhat to focus on at each stage:\n\n|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|\n| Date | Milestone | Developer focus |\n| August 2025 | New Android developer verification requirements [announced](https://android-developers.googleblog.com/2025/08/elevating-android-security.html) | Learn about the new requirements and sign up for early access. |\n| October 2025 | Early access begins | If invited, start your identity verification and app registration. |\n| March 2026 | Registration opens for all developers | Begin your identity verification and app registration for all apps you want to remain installable on certified Android devices. |\n| September 2026 | Regional enforcement begins | Verify compliance to avoid installation blocks on your apps in Brazil, Indonesia, Singapore, and Thailand. |\n| 2027 and beyond | Global enforcement | The rollout continues worldwide. |\n\nKey concepts\n------------\n\nBefore you start, review these key terms:\n\n- **Identity verification**: The process of providing information and official documentation to verify your identity as an individual or organization.\n- **Package name registration**: The process of creating a formal, verifiable link between your app's unique package name and signing keys.\n- **App signing key** : The certificate used to [sign your APK](/studio/publish/app-signing).\n- **Certified Android devices** : Google enforces Android developer verification requirements on these devices. If your app runs on a [certified device](https://www.android.com/certified/), these requirements apply to you, regardless of your app's download source.\n- **Android Developer Console (ADC)**: A console for developers who distribute apps only outside of Google Play.\n- **Google Play Console (PDC)**: The console for developers who distribute apps on Google Play. If you have a Play Console account, use it to complete the verification requirements.\n\nFind your path\n--------------\n\nUse the following table to find the correct console and instructions for your\nsituation.\n\n|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| [Sign up for early access](https://goo.gle/android-verification-early-access) to the Android developer verification experience. You might receive an invitation to our invite-only early access. |\n\n|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|\n| **If you distribute apps**... | **Next Steps** |\n| **Only on Google Play** | Use your existing [Play Console account](/developer-verification/guides/google-play-console). |\n| **Both on and off Google Play** | Use your existing [Play Console account](/developer-verification/guides/google-play-console). A new option lets you register your non-Play apps and keys. |\n| **Only outside of Google Play** | Create an account in the [Android Developer Console](/developer-verification/guides/android-developer-console). |"]]