Google Play 管理中心阻止上传或推广符合敏感权限政策的新应用版本

Question

我有一个现有应用已发布到需要 SMS 权限的正式版和 Beta 版轨道。为了遵守 Google 最近对这些权限的政策更改，我删除了所有 SMS 权限，并在内部测试和 alpha 轨道中拥有不需要这些权限的更高版本代码的新版本。

我无法将这些合规版本提升为测试版或正式版，也无法将新的更高版本直接上传到测试版或正式版。我总是看到红色的 "changes cannot be saved" 栏。我无法按照 Google、"Alternatively, consider deactivating any Open, Closed, or Internal testing tracks that are not currently in use if they are not compliant with this policy." 的建议从 Beta 轨道禁用或删除测试人员 我也没有在控制台的任何地方看到 "Permissions Declaration Form"。

Play 控制台似乎让我陷入了一个循环，我“...在您创建一个新的应用程序版本声明敏感权限之前无法编辑此应用程序。”而且我无法创建新的应用程序版本，因为我无法编辑该应用程序。

我只是想发布一个新的更高版本的我的应用程序，删除了 SMS 权限，而不是根据需要声明它们。有什么建议吗？

Answer 1

来自this post：

I finally got this to work. I created a new release but didnt upload a new APK, in this release I deactivated all the previous APKs except the current one. In this release form you are presented with a sensitive permissions declaration form on which i declared that the release did not comply with the new regulations. (This prompts a warning that you must comply before march 19). After rolling out this release, which basically changed nothing because no new APK was made available, I created a new release with the new APK that I wanted to publish, this went on normally and is currently in rollout.

也请尝试此 link 中的其他解决方案。

Answer 2

刚遇到完全相同的问题。
如果不接受内联许可声明表，似乎没有办法解决它。

我解决问题的方法是：

1. 在目标频道中单击创建版本。
2. 上传更高版本的新 APK，并删除短信权限。
3. [重要] 在上一版本（包含 SMS 权限的版本）上单击 RETAIN - 将显示内联 权限声明表 .
4. 在权限声明表中，在Compliance status下（此版本是否符合短信和通话记录权限策略？如果您选择否，您可以在没有 select 任何核心功能的情况下提交表单。), select 否，此版本不符合短信和通话记录权限政策.
5. 选中 Declarations 下的所有复选框（通过提交此权限声明表，我确认）。
6. 单击保存，然后单击查看按钮。
7. 您将被导航至 Review and rollout screen，Rollout 按钮将最终启用。

为了删除保留的版本（从第 3 步开始 - 包含 SMS 权限的版本），您可以创建另一个版本（具有更高版本的 APK）- 您可以在其中停用任何以前的版本。

Answer 3

我刚刚意识到我的过程有点不同：

1. Ensure Alpha or Beta track does not have OLD APK with permissions violations.
2. If it does, Delete/Deactive the Beta and Alpha ones before uploading a new one to Production.
3. If you can't simply delete or deactivate an Alpha or Beta release, which some are finding to the be the problem (as was my problem), then you must overwrite the existing Alpha/Beta versions with a new version...that forces the Alpha/Beta to auto-deactivate.
4. Alpha/Beta Manage -> Create Release -> upload a new APK (even if its to be your next Production version)
5. Ensure the previous one is showing Deactivated, then Save, Review and Release. I got all kinds of warnings/severe warnings about not having Alpha user lists and not being deployed to thousands of devices. I ignore those and released anyway.
6. I never got a Restricted Permissions Form on my newly uploaded APK because I had already removed the need for them in my app.
7. After the old one is gone, then go back into that Alpha/Beta release you just created and Promote to Production - SAVE, REVIEW, RELEASE again.

希望这对外面的人有所帮助。我花了 2 个小时的挫折才终于解决了这个烂摊子。

Google 应该只允许您删除 Alpha/Beta 版本 - 或者更具体地说，甚至不认为它们是有效的生产......或者更重要的是，LABEL 哪些版本没有通过要求.我花了一个小时才弄清楚这是一个 1.5 年前的 Alpha 版本正在对我进行冲洗。