我的应用程序是在React Native中开发的,并在Playstore上发布.
So First time when it’s showing warning for RECEIVE_SMS
我删除了与此权限相关的插件,并相应地更改了我的工作流程.并再次上传更新的apk到Playstore.
我仍然收到Google Play的最终警告邮件,邮件如下: –
In October 2018, we announced updates to our Permissions policy that
will limit which apps are allowed to request Call Log and SMS
permissions. This is the third and final reminder to let you know that
this policy may impact one or more of your apps.Starting January 9, 2019, only an app that has been selected as a
user’s default app for making calls or text messages, or whose core
functionality is approved for one of the exception use cases, will be
able to access Call Log or SMS permissions.
我找到了整个项目,我没有获得任何插件的RECEIVE_SMS权限.
这是我的清单代码: –
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW"/>
<uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" />
<uses-permission android:name="android.permission.VIBRATE" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
<uses-permission android:name="android.permission.WAKE_LOCK" />
<permission
android:name="${applicationId}.permission.C2D_MESSAGE"
android:protectionLevel="signature" />
<uses-permission android:name="${applicationId}.permission.C2D_MESSAGE" />
这是我用过的插件: –
"dependencies": {
"lodash": "^4.17.10",
"moment": "^2.22.2",
"moment-duration-format": "^2.2.2",
"prop-types": "^15.6.2",
"react": "16.4.1",
"react-native": "0.56.0",
"react-native-actionsheet": "^2.4.2",
"react-native-autocomplete-input": "^3.6.0",
"react-native-background-timer": "^2.0.1",
"react-native-check-box": "^2.1.0",
"react-native-confirmation-code-input": "^1.0.4",
"react-native-datepicker": "^1.7.2",
"react-native-device-info": "^0.24.3",
"react-native-dropdownalert": "^3.5.0",
"react-native-fabric": "github:corymsmith/react-native-fabric#523a4edab3b2bf55ea9eeea2cf0dde82c5c29dd4",
"react-native-firebase": "^4.3.8",
"react-native-google-sign-in": "^1.0.16",
"react-native-keyboard-aware-scroll-view": "^0.7.0",
"react-native-material-dialog": "^0.7.4",
"react-native-message-bar": "^2.0.10",
"react-native-modal": "^6.5.0",
"react-native-pages": "^0.7.0",
"react-native-progress": "^3.5.0",
"react-native-simple-radio-button": "^2.7.2",
"react-native-snackbar": "^0.5.0",
"react-native-social-auth": "^2.0.0",
"react-native-splash-screen": "^3.1.1",
"react-native-stars": "^1.1.5",
"react-native-swiper": "^1.5.13",
"react-native-tab-view": "^1.0.2",
"react-native-toast": "^1.0.1",
"react-native-vector-icons": "^5.0.0",
"react-native-web-service-handler": "^1.0.2",
"react-navigation": "^2.11.2"
},
我正在使用以下流程查找权限: –
>我尝试使用不同的工具和编辑器使用所有搜索方法来查找此权限
>还手动检查所有插件清单文件.
>创建发布apk后,从build文件夹中检查清单.
我仍然无法找到这一点,从这个权限包括在apk中.
所以我的问题是,
>我怎样才能找到这个权限包含在我的apk中?
>使用搜索方法时,我能够在node_modules / react native / Libraries / PermissionAndroid Module中找到RECEIVE_SMS权限.但我没有在我的项目中使用或导入该类.它是否会产生问题?
请帮助我或指导我,如何构建没有CALL / SMS权限的apk以及React Native的任何调试方法来检查它?
提前致谢.
最佳答案 我们遇到了同样的问题.事实证明,我们在alpha通道中仍然有一个非常老的应用程序版本.删除修复警告.
全文:我们使用READ_SMS权限进行登录,然后看到有关新策略的博客文章,并决定将其删除,因为此用法不符合要求.删除并更新了Play商店中的apk.
当我们添加另一个功能并上传新的APK并获得有关SMS的警告以及询问我们为什么要使用它的表单时,第一个暗示出现了什么问题.由于我们不是,所以我们决定回答我们不合规,因为我们没有使用READ_SMS,因此不需要兼容.
今天我们发出最后警告,即我们仍在使用READ_SMS权限,如果不修复,应用程序将在2019年3月9日删除.
经过调查,我们发现新的APK和发布频道已经很长时间了.但是我们从两年前开始有一个活跃的alpha版本,它仍在使用READ_SMS权限.在我们停用后,警告立即消失.