How to Read App Health Check Reports
A Health Check report tells you what to fix and in what order. Here is exactly how to read it, what each severity level means, and how to prioritise your fixes.
Severity levels explained
Will cause immediate automated rejection before human review. Do not submit until every Critical finding is resolved.
Examples
Debug build submitted instead of release build
Missing PrivacyInfo.xcprivacy (iOS)
targetSdkVersion below Play Store minimum
App icon missing or has alpha channel
Will likely trigger rejection during human review. Should be fixed before submission in almost all cases.
Examples
Cleartext HTTP traffic allowed
Permissions declared but not used in the app
Screenshots don't match the submitted build
May trigger a reviewer request for clarification or a review note. Recommended to fix but won't always cause outright rejection.
Examples
Usage description strings are generic ('Required') rather than descriptive
Privacy policy URL returns a redirect rather than the final page
Best practice recommendations. Not rejection risks but represent opportunities to improve your app's compliance posture.
Examples
Consider enabling certificate pinning for sensitive data flows
App doesn't include a 'Manage Subscription' link in settings
How to work through a report
Fix all Critical findings first
These are automatic rejections. Nothing else matters until Critical issues are resolved. Re-build and re-scan before moving on.
Address all High findings
High findings will likely cause rejection at human review. Fix these before submission.
Review Medium findings
Assess each Medium finding individually. Most should be fixed. Some may have context-specific reasons: the report will include the relevant policy link to help you decide.
Read Informational findings
These are best practice improvements. Not urgent, but note them for your next update cycle.
Re-run the scan after fixes
After fixing Critical and High issues, rebuild your release binary and run the Health Check again. This confirms your fixes are present in the binary, not just in source code.
Run a Health Check before your next submission
Free. 30 seconds. Upload your APK, AAB, or IPA and get a severity-ranked report.
Free Health Check