Repository navigation
|
How can a team catch Android backup is enabled without filtering sensitive data 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 -rn 'allowBackup="true"' . && ! grep -rn 'dataExtractionRules\|fullBackupContent\|allowBackup="false"' .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. android:allowBackup is set to true in AndroidManifest.xml without setting data extraction rules to exclude credentials/databases. The fix. Disable backups with allowBackup="false", or configure dataExtractionRules / fullBackupContent to exclude sensitive credentials and SQLite databases. 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
ANDROID-INSECURE-BACKUPwith a coverage line and a proper exit code.What the hit means. android:allowBackup is set to true in AndroidManifest.xml without setting data extraction rules to exclude credentials/databases.
The fix. Disable backups with allowBackup="false", or configure…