谷歌商店上架APP被拒绝 _拒绝

听闻少年二字，当与平庸相斥。这篇文章主要讲述谷歌商店上架APP被拒绝相关的知识，希望能为你提供帮助。
Google Play Store 应用被强制下架/更新被拒绝(权限 RECEIVE_SMS) 　强制下架/更新失败原因谷歌对应用权限增加了限制,其中电话和短信相关的权限会导致应用被下架或是应有更新失败

敏感权限如下
活动	要求
您的应用清单请求“ 通话记录” 权限组（例如 READ_CALL_LOG、WRITE_CALL_LOG、ROCESS_OUTGOING_CALLS）	必须由用户主动将应用注册为设备的默认电话或辅助处理程序。
您的应用清单请求“ 短信” 权限组（例如 READ_SMS、SEND_SMS、WRITE_SMS、RECEIVE_SMS、RECEIVE_WAP_PUSH、RECEIVE_MMS）	必须由用户主动将应用注册为设备的默认短信或辅助处理程序。

Google Play 拒绝原因

Issue: Violation of Permissions policy

After reviewing your app, we found that it doesn’ t qualify to use the requested permissions for the following reason(s):

Your app must prompt the user for permission access via a runtime permission; if your app is a default handler the default handler prompt must precede the runtime permission.

Based on our review, your app doesn’ t appear to properly prompt the user to approve related permissions. You can come into compliance by either removing the permission(s) from your app or by adding the appropriate prompt. For additional guidance, please review the documentation on how to request app permissions
Your app needs to use runtime permissions for us to complete the review. Please update your app to target API level 26 or above. If you have APKs in different tracks of the app releases section of your Play Console, please deactivate non-compliant APKs before submitting your app again. For additional guidance, please review the documentation on how to request app permissions.

附Google截图

文章图片

解决方案删除应用中相关的权限或用其他实现方案
一般删除掉这些权限谷歌就会放行APP.
但是还有些特殊情况
当应用中集成了MobSDK 会发现清单文件并没有RECEIVE_SMS相关权限,可是APP在提交后谷歌检测出APP所需权限仍然包含,这时候就需要我们主动去移除这些权限

在项目gradle文件根目录添加排除RECEIVE_SMS的代码

MobSDK { appKey "**********" appSecret "*****************" gui false permissions { exclude "android.permission.RECEIVE_SMS" } }

这时会发现本来提示的RECEIVE_SMS权限已经被移除
如有其他三方sdk 包含敏感权限也可参照此方法
注意: 项目上架还存在一个注意点当应用被下架/更新失败后,提交新的正确的apk后仍提示存在风险权限,那么需要注意一下测试版本是否替换,如果测试版或是其他什么版本还是不符合规格的apk,同样是无法更新成功.所以这里要确保新提交的每个版本都是修改过的apk
最后经过上述修改,APP成功上架.
【谷歌商店上架APP被拒绝】