当我的应用程序不包含它时,query_all_all_packages权限问题
我的旧版本我的应用程序包含query_all_packages许可,但是在发送给我的Google电子邮件发送给我说我无法在应用程序中使用此权限后,我将其删除并检查我的应用程序是否仍然有许可,我敢肯定我的应用程序没有许可,而Google仍在使用QUERY_ALL_PACKAGES许可问题接受我的应用程序,说我不得使用我已经删除的权限。
您可以检查我是否错过了底部的屏幕截图中的任何内容
和
我还尝试将以下行添加到我的androidManifest.xml文件中
<uses-permission android:name="android.permission.QUERY_ALL_PACKAGES" tools:node="remove" tools:ignore="QueryAllPackagesPermission" />
My old version of my app contained QUERY_ALL_PACKAGES permission but after the Google email sent to me saying that I can't use this permission in my app so I deleted it and I check if my apps still have the permission or not and I'm sure that my app does not have the permission and Google still accepting my app with QUERY_ALL_PACKAGES permission issue saying that I must not use the permission that I already deleted.
you can check if I missed anything from screenshots in the bottom
release details from google play console
and
permission from a device after installing the app
I also tried to add the following line to my AndroidManifest.xml file
<uses-permission android:name="android.permission.QUERY_ALL_PACKAGES" tools:node="remove" tools:ignore="QueryAllPackagesPermission" />
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
正如我们在评论中讨论的那样,您还需要检查您的“内部测试”,“封闭测试”和“开放测试”发行轨道。如果这些曲目仍然包含使用此权限的应用程序的版本,则需要创建新版本来取代这些版本。
另外,了解即使您更新了所有发布曲目,您仍可能会收到拒绝电子邮件。这是因为自动评论可能会在另一个轨道之前完成。因此,评论失败了,因为它尚未考虑其他发行曲目上的新版本。
As we discussed in the comments, you need to also check your "Internal Testing", "Closed Testing", and "Open Testing" release tracks. If these tracks still contain versions of the app that use this permission, you'll need to create new releases to supersede those versions.
Also, understand that you might still get a rejection email even after you've updated all release tracks. This is because the automated review might finish for one track before the others. So the review fails because it's not yet considering the new versions on your other release tracks.