Google Play Console Permissions Headache: Why READ_CALL_LOG Still Shows Even After Updating Your APK
Problem: You've meticulously removed the READ_CALL_LOG permission from your Android app, rebuilt your APK, and uploaded it to the Google Play Console. Yet, the pesky Permissions Declaration Form continues to display the READ_CALL_LOG permission, even though your app no longer requires it. This leaves you frustrated and worried about Google Play's review process.
Scenario: Imagine you developed an app that initially required access to call logs for a specific feature. Later, you decided to remove this feature altogether. You updated your code to remove the READ_CALL_LOG permission request, rebuilt your APK, and uploaded it to the Google Play Console. To your dismay, the Permissions Declaration Form still lists READ_CALL_LOG as a required permission.
Original Code (Example):
// Before removing READ_CALL_LOG
if (ContextCompat.checkSelfPermission(this, Manifest.permission.READ_CALL_LOG)
!= PackageManager.PERMISSION_GRANTED) {
ActivityCompat.requestPermissions(this,
new String[]{Manifest.permission.READ_CALL_LOG},
MY_PERMISSIONS_REQUEST_READ_CALL_LOG);
}
The Culprit: Google Play's Permission Caching
The issue lies in the way Google Play Console caches permission information. When you upload an APK, the Console extracts permission information, which is used for displaying the Permissions Declaration Form. This cached information can persist even after you remove permissions from your app and upload a new APK.
Troubleshooting & Solutions:
-
Clear the Cache: The most effective solution is to clear the cached permission information in the Google Play Console. You can do this by:
- Navigating to the App Content section.
- Selecting your app.
- Clicking on the Permissions tab.
- Clicking the Clear Cache button at the top.
- Re-uploading your APK.
-
Submit a New APK: In some cases, simply re-uploading the updated APK may be enough to trigger a re-evaluation of permissions. However, this is not guaranteed.
-
Contact Support: If the issue persists, reach out to Google Play Console support. They can investigate the problem and offer further assistance.
-
Double-Check Your Code: Verify that you have completely removed all references to
READ_CALL_LOGin your code, including permission requests, usage within functions, and any dependencies that might still access this permission.
Additional Insights:
- The cache clearing process may take some time for Google Play to process.
- Google Play Console's caching mechanism helps speed up the review process, but it can sometimes lead to these discrepancies.
- It's crucial to regularly review and update your app's permission requirements, as they can change over time.
Remember: Always strive to obtain only the permissions your app truly needs. This not only ensures a smoother Play Store experience but also enhances user privacy and trust.
Resources:
- Google Play Console Help
- Google Play Console Permissions Documentation
- Android Developer Documentation: Permissions
By understanding the reasons behind this issue and following these steps, you can successfully resolve the READ_CALL_LOG permission display error and move forward with a streamlined Play Store submission process.
