apple-store-submitlisted

Handle Apple App Store rejection emails end-to-end — parse rejection reasons, create a fix plan, implement code changes (privacy strings, entitlements, sandbox), navigate App Store Connect to update metadata, and resubmit. Use when an app receives a rejection or when preparing a first-time submission.
oleg-koval/agent-skills · ★ 2 · AI & Automation · score 74

Install: claude install-skill oleg-koval/agent-skills

> 🤖 *Auto-generated by **weekly-pattern-learner** · App Store rejection handling workflow observed in FocusNotch App Store session, Jun 2026 (92 user turns covering rejection → plan → code fixes → metadata → resubmit)* # Apple App Store Submission & Rejection Handling ## Overview Parse Apple rejection feedback, implement targeted fixes, update App Store Connect metadata, and resubmit — covering the complete cycle from rejection email to approved build. ## When to Use - Apple review team sends a rejection email - App fails automated pre-review checks (binary rejected at upload) - Preparing metadata for first-time submission (screenshots, keywords, privacy labels) - Resolving App Store Connect errors before submitting for review ## Workflow ### 1. Parse the Rejection Read the full rejection email. Extract and list: - **Guideline numbers** violated (e.g., 2.1, 4.2.0, 5.1.1) - **Code-level issues** — missing entitlements, incorrect privacy strings, sandbox violations - **Metadata issues** — wrong screenshot sizes, subtitle policy, keyword stuffing - **UX issues** — crashes described by reviewer, broken flows, missing functionality Create a numbered fix plan: one item per rejection point, with the type of fix needed. ### 2. Classify Fixes by Type | Type | Location | |------|----------| | Privacy usage strings missing | `Info.plist` | | Entitlement missing/wrong | `<AppName>.entitlements` | | Crash or broken feature | Source code | | Screenshots wrong size/content | Ap