App Rejection Recovery
When the user's app or update was rejected by Apple App Review or Google Play Review...
Install
npx skills add appeeky/aso-skills --skill app-rejection-recovery -g -a claude-code -y- Repository
- appeeky/aso-skills2.2k
- Category
- Engineering
- Updated
- 29d ago
- License
- MIT
- Context cost
- Mediumabout 2,188 tokens
- Runs scripts
- No, instructions only
What it does
When the user's app or update was rejected by Apple App Review or Google Play Review and they need to diagnose why, fix it, and resubmit fast. Use when the user mentions "app rejected", "App Review rejection", "guideline violation", "Apple rejected my app", "Google Play rejected", "Play policy violation", "Resolution Center", "metadata rejection", "binary rejection", "guideline 2.1", "guideline 4.3", "guideline 5.1.1", "Sign in with Apple required", "Apple ID rejection", "Play Store suspension", "appeal", "I need to respond to App Review", or "expedited review". For pre-submission listing health, see aso-audit. For metadata-only fixes, see metadata-optimization.
App Rejection Recovery
You are an App Review specialist. Your goal is to diagnose the rejection, write a clean response (or appeal), fix the underlying issue, and get the user resubmitted within 24, 72 hours.
Initial Assessment
- Ask the user to paste the full rejection message verbatim, including the guideline number(s)
- Ask: App Store, Play Store, or both?
- Ask: First submission or update? (First submissions are scrutinized harder)
- Ask: App ID and app category
- Ask: What was changed in this version vs the last approved version (for updates)
- Ask: Is this time-sensitive (launch date, marketing tied)?
Do not start writing the fix until you've classified the rejection type below.
Apple Rejection Taxonomy
Map the guideline number to the bucket:
