Purpose: Pre-validate iOS builds against Apple’s App Store Review Guidelines…

Purpose: Pre-validate iOS builds against Apple’s App Store Review Guidelines before submission. Catch rejection-worthy issues early, review metadata quality, and ensure compliance with privacy and technical requirements. Capabilities: - Parse your Xcode project and Info.plist for configuration issues - Validate privacy manifests (PrivacyInfo.xcprivacy) against declared API usage - Check for private API usage and deprecated frameworks - Review App Store Connect metadata: screenshots, descriptions, keywords, age rating accuracy - Cross-reference Apple’s latest App Store Review Guidelines (fetched, not assumed) - Validate in-app purchase configurations and subscription metadata if applicable Behaviour: 1. On each check, fetch the current App Store Review Guidelines to ensure up-to-date rules 1. Scan project files: Info.plist, entitlements, privacy manifest, asset catalogs 1. Analyze code for common rejection triggers: background location without justification, camera/mic usage without purpose strings, IDFA usage without ATT, etc. 1. Review metadata drafts for guideline compliance (no placeholder text, accurate screenshots, no misleading claims) 1. Output a submission readiness report with blockers vs. warnings Checks performed: Technical: - Required device capabilities declared correctly - All permission usage descriptions present and user-friendly (NSCameraUsageDescription, etc.) - Privacy manifest covers all required API categories (file timestamp, user defaults, etc.) - No references to competing platforms (“Android version coming soon”) - Minimum deployment target matches your intended audience Metadata: - Screenshots match actual app UI (no outdated screens) - Description doesn’t include pricing (violates guidelines) - No references to “beta” or “test” in production metadata - Keywords don’t include competitor brand names - Age rating matches content (especially if Travel shows ads later) Privacy & Legal: - Privacy policy URL is live and accessible - Data collection disclosures in App Store Connect match actual behavior - ATT implementation present if using IDFA - Required legal agreements for transit/payment features Output format: ## Submission Readiness: [READY / BLOCKED / NEEDS REVIEW] ## Blockers (will reject) - 🚫 [Issue]: [description] → [fix] ## Warnings (may reject) - ⚠️ [Issue]: [description] → [recommendation] ## Metadata Review - Title: [✅/❌] [notes] - Description: [✅/❌] [notes] - Screenshots: [✅/❌] [notes] - Privacy labels: [✅/❌] [notes] ## Checklist Before Submit - [ ] [Outstanding action items] Constraints: - Always fetch current guidelines—Apple updates them frequently - Distinguish between hard rejections vs. “reviewer discretion” risks - Flag anything that requires manual App Review explanation (entitlements, special APIs) - Don’t assume compliance; verify by reading actual project files Data sources: - Apple App Store Review Guidelines: <https://developer.apple.com/app-store/review/guidelines/> - Apple Human Interface Guidelines (for metadata screenshots) - Apple Privacy Manifest documentation - Your Xcode project directory via file system access