As per the developer policy, it was recommended not to use SMS and CALL_LOG related permissions, unless the app has core functionality related to them. I was previously using READ_SMS permission to auto-detect OTP, but later removed it from the application & replaced it with SMS Retriever API. I published the application without any prohibited permission to play store on 3rd Jan 2019, before the deadline that required the app to be updated without those permissions before 9th January 2019. Now when I try to update the app with a new release to play store I get an app release error that 1 error needs to fixed.When I clicked to see the error details the message is "You can't edit this app until you create a new app release declaring sensitive permissions."
Currently the list of permissions used in my app are as follows:-
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.GET_ACCOUNTS" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/> <uses-permission android:name="android.permission.CAMERA" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" /> <uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/> <uses-permission android:name="android.permission.VIBRATE" />
<uses-permission android:name="android.permission.SYSTEM_ALERT_WINDOW" /> <uses-permission android:name="android.permission.READ_CONTACTS" />
<uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED"/> <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" /> <uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION"/> <uses-permission android:name="android.permission.RECORD_AUDIO" />
I'm not using any SMS or CALL_LOG permission, but still face an error while publishing new release.Please refer the links to view the error.
App Error while publishing new release
The company says that the decision to monitor phone logs and SMS permissions is to protect user privacy.
Your app can't use SMS without the SEND_SMS permission line in AndroidManifest. xml. This permission line enables a setting for the app in the Settings app that gives the user the choice of allowing or disallowing use of SMS.
Most of these are pretty self-explanatory---for instance, the SMS permission lets apps read and send text messages---but you'll see descriptions at the top of each page if you're not sure. Tap a permission and under Allowed, you'll see every app that you've approved to use that function.
I checked the 'Artifact Library' section, which is under 'Release Management' on app publishing dashboard.
I carefully examined every 'Active Artifact' and found one live artifact that was released on Open Track(Beta),which wasn't pushed to production. This active artifact which was a beta release long ago had READ_SMS permission, which was responsible for the warning.
So in order to tackle this I rolled out my app without SMS or CALL_LOG permission to testing track on Beta.
From Beta I released it to production, and I was able to publish my app to production.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With