Repository navigation
|
My app was flagged or rejected on Google Play for this. SMS or Call Log without an approved core use case. Which guideline is this, how do I find it in my project, and how do I fix it before I resubmit? |
Replies: 1 comment
|
Guideline. Permissions and APIs (Google Play) Severity in the playbook. critical What triggers it. READ_SMS, SEND_SMS, RECEIVE_SMS, READ_CALL_LOG, or WRITE_CALL_LOG declared without an approved use case. From 26 August 2026 account verification via phone call is no longer a permitted use case for READ_CALL_LOG. Use the Digital Credentials API or the SMS Retriever API instead. What to search your code for. How to fix it. Use the permissions declaration form for an approved core use case, or drop the permission. The guard reports this as This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
Guideline. Permissions and APIs (Google Play)
Severity in the playbook. critical
What triggers it. READ_SMS, SEND_SMS, RECEIVE_SMS, READ_CALL_LOG, or WRITE_CALL_LOG declared without an approved use case. From 26 August 2026 account verification via phone call is no longer a permitted use case for READ_CALL_LOG. Use the Digital Credentials API or the SMS Retriever API instead.
What to search your code for.
READ_SMS,SEND_SMS,RECEIVE_SMS,READ_CALL_LOG,WRITE_CALL_LOGHow to fix it. Use the permissions declaration form for an approved core use case, or drop the permission.
The guard reports this as
GOOGLE-PERM-SMS-CALLLOG. The full pattern is in data/rejection-patterns.json.This is a mai…