Repository navigation
|
How can a team catch SMS or Call Log without an approved core use case automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rnE 'permission.(READ_SMS|SEND_SMS|RECEIVE_SMS|READ_CALL_LOG|WRITE_CALL_LOG)' --include='AndroidManifest.xml' .Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. 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. The fix. Use the permissions declaration form for an approved core use case, or drop the permission. Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
GOOGLE-PERM-SMS-CALLLOGwith a coverage line and a proper exit code.What the hit means. 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…