App Store Submission Skill

Automates and validates the complete iOS App Store submission process, from code auditing to final upload.

Quick Start

When a user requests App Store submission help, follow this workflow:

1. Project Analysis - Scan the Xcode project for configuration and code issues
2. Compliance Check - Validate privacy, accessibility, and App Store requirements
3. Asset Validation - Check for required assets (app icon, screenshots)
4. Submission Checklist - Generate actionable checklist with priorities
5. Timeline Estimation - Provide realistic timeline based on current state

Core Capabilities

1. Pre-Submission Code Audit

Run comprehensive checks for common App Store rejection causes:

Privacy & Permissions:

• Validate all Info.plist usage descriptions (Camera, Photo Library, Location, etc.)
• Check for NSPhotoLibraryAddUsageDescription if app shares/saves content
• Verify privacy manifest requirements for required APIs
• Ensure descriptions are user-friendly (not technical)

Code Quality Issues:

• Thread safety violations (@MainActor usage, background thread UI updates)
• Infinite loop risks in calculations/iterations
• Memory leaks and retain cycles
• Force unwrapping and optional misuse
• Missing accessibility labels on interactive elements
• Input validation gaps

Architecture & Best Practices:

• SwiftUI state management anti-patterns
• Unbounded data structures (memory issues)
• Deprecated API usage
• Error handling completeness

2. Compliance Validation

Required Configurations:

• App icon (all required sizes in Assets.xcassets)
• Bundle identifier format validation
• Version and build number consistency
• Code signing configuration
• Deployment target appropriateness

Privacy Requirements:

• Privacy manifest file (PrivacyInfo.xcprivacy) if using required APIs
• Privacy policy URL if collecting user data
• Data collection transparency

Accessibility:

• All interactive elements have accessibility labels
• VoiceOver navigation support
• Dynamic type support where appropriate

3. Asset Preparation Guidance

App Icon Requirements:

• 1024x1024px App Store icon
• All required app icon sizes in Assets.xcassets
• Proper alpha channel handling (no transparency)

Screenshot Requirements:

• Required device sizes (6.5", 6.7", 5.5" iPhones, iPad Pro)
• Localized screenshots if supporting multiple languages
• Recommended: 3-5 screenshots showing key features

4. Build Configuration Check

Validate build settings for release:

• Code signing identity and provisioning profile
• Build optimizations enabled
• Debug symbols configuration
• Entitlements validation

5. Common Rejection Patterns

Scan for patterns that frequently cause rejections:

Technical Issues:

• Crashes on launch or during basic functionality
• Broken links or placeholder content
• Incomplete features (non-functional buttons)
• Performance issues (excessive battery drain, memory usage)

Content Issues:

• Placeholder text or "Lorem ipsum"
• Missing content for advertised features
• Inappropriate or offensive content

Guideline Violations:

• Metadata inconsistencies (description doesn't match functionality)
• Misleading screenshots
• Hidden features not disclosed

Workflow Examples

Example 1: Initial Submission Audit

User: "I'm ready to submit my app to the App Store. Can you check if everything is ready?"

Process:

1. Scan for .xcodeproj or .xcworkspace
2. Check project.pbxproj for bundle ID, version, build settings
3. Validate Info.plist or build settings for privacy strings
4. Check Assets.xcassets for app icon
5. Scan code for critical issues (use references/code-audit-checklist.md)
6. Generate prioritized checklist with time estimates
7. Provide actionable next steps

Example 2: Fix Specific Issue

User: "Apple rejected my app saying the privacy description is too technical"

Process:

1. Locate privacy descriptions in build settings or Info.plist
2. Review for technical jargon
3. Suggest user-friendly alternatives
4. Provide code/configuration updates

Example 3: Timeline Estimation

User: "How long until I can submit?"

Process:

1. Analyze current state
2. Identify all blockers (critical, high, medium priority)
3. Estimate time per issue
4. Account for Apple review time (typically 1-3 days)
5. Provide optimistic, realistic, and conservative timelines

Validation Scripts

The skill includes Python scripts for automated validation:

scripts/validate_privacy.py

Checks Info.plist and build settings for required privacy descriptions

scripts/validate_assets.py

Validates app icon sizes and screenshot requirements

scripts/analyze_xcode_project.py

Extracts configuration from Xcode project files

Reference Materials

Detailed Checklists

• references/code-audit-checklist.md - Comprehensive code quality checks
• references/privacy-checklist.md - Privacy and permissions validation
• references/rejection-patterns.md - Database of common rejection reasons with fixes
• references/privacy-strings-examples.md - User-friendly privacy description templates

Best Practices

When Auditing Code

1. Start with blockers - Focus on critical issues that will cause instant rejection
2. Check in order: Privacy → Code Quality → Assets → Metadata
3. Provide specific file:line references when identifying issues
4. Suggest fixes, not just problems - Include code snippets for solutions
5. Estimate effort realistically - Account for testing time

When Generating Checklists

1. Prioritize by impact - CRITICAL → HIGH → MEDIUM → LOW
2. Group related items - Bundle similar fixes together
3. Provide time estimates - Help user plan submission timeline
4. Include verification steps - How to confirm each fix works

When Providing Privacy Strings

1. User-centric language - Explain benefits, not technical requirements
2. Be specific - "take photos for your profile" vs "camera access"
3. Emphasize value - "personalize reports" vs "store images"
4. Avoid jargon - No mentions of "API", "background processing", etc.

Output Formats

Submission Readiness Report

# App Store Submission Status
**App Name**: [App Name]
**Bundle ID**: [com.company.app]
**Current Status**: [X]% Ready

## ✅ Passing (What's Working)
- Clean build with zero warnings
- All tests passing
- Code signing configured
...

## ⚠️ Issues Found
| Priority | Issue | File | Estimated Fix Time |
|----------|-------|------|-------------------|
| CRITICAL | Missing app icon | Assets.xcassets | 1-2 hours |
...

## 📋 Action Items
1. [CRITICAL] Create app icon (1-2 hours)
2. [HIGH] Add privacy manifest (30 min)
...

## ⏱️ Timeline Estimate
- Optimistic: 2-3 days
- Realistic: 3-5 days
- Conservative: 5-7 days
(Including Apple review: +1-3 days)

Issue Detail Format

For each identified issue:

### [Priority] Issue Title
**File**: path/to/file.swift
**Lines**: 123-145
**Risk**: What could go wrong
**Fix**: Specific solution with code example
**Verification**: How to test the fix worked

Advanced Features

Xcode Project Parsing

Parse .pbxproj files to extract:

• Bundle identifier
• Version and build numbers
• Build configurations
• Entitlements
• Frameworks and dependencies
• Privacy usage descriptions

Build Settings Analysis

Analyze build settings for:

• Code signing configuration
• Deployment target
• Architecture settings (arm64)
• Optimization levels
• Swift version

Automated Fix Suggestions

For common issues, provide executable solutions:

• Privacy string templates ready to copy
• Code snippets with proper thread safety
• Accessibility label examples
• Input validation patterns

Integration with Claude Code

When used via Claude Code (terminal-based development):

1. Respect file locations - Read from actual project paths
2. Generate diffs - Show before/after for proposed changes
3. Create fix scripts - When appropriate, generate one-time scripts for bulk fixes
4. Update multiple files - Handle multi-file fixes in single operation
5. Preserve formatting - Maintain existing code style and conventions

Tips for Success

1. Run audit early - Don't wait until submission day
2. Fix critical issues first - Some issues block submission entirely
3. Test fixes thoroughly - Build and run after each major change
4. Document changes - Keep track of what was fixed for resubmissions
5. Plan for iteration - First submission may be rejected; have time buffer

Version-Specific Notes

iOS 18+:

• Privacy manifest required for certain APIs
• Enhanced privacy descriptions expected

Xcode 15+:

• Build settings location changed (often in .pbxproj vs Info.plist)
• Asset catalog requirements stricter

App Store Review Guidelines (Latest):

• Increased scrutiny on data collection
• Stricter enforcement of metadata accuracy
• Enhanced accessibility requirements

Limitations

This skill does NOT:

• Test the actual app (user must do manual testing)
• Generate app icons or screenshots (user must create assets)
• Submit to App Store Connect (user must do final submission)
• Make changes without user approval (always suggests, never modifies directly without confirmation)

Next Steps After This Skill

Once submission is complete:

1. Monitor App Store Connect for review status
2. Respond promptly to any App Review questions
3. Plan for post-approval marketing
4. Prepare for updates and maintenance

---

Remember: This skill provides guidance and validation. Always review suggestions carefully and test thoroughly before submitting.