Metadata Rejected on the App Store: What It Means and How to Fix It Fast
Metadata Rejected means Apple flagged your listing — screenshots, description, URLs, or a missing demo account — not your build. Here's how it differs from a binary rejection, and how to fix it without a new build.
Metadata Rejected on the App Store: What It Means and How to Fix It Fast
Metadata Rejected means Apple flagged your listing — screenshots, description, URLs, or a missing demo account — not your build. Here's how it differs from a binary rejection, and how to fix it without a new build.
What 'Metadata Rejected' Actually Means
When Apple rejects your submission with 'Metadata Rejected', it means the issue is with your App Store Connect listing information — not the app binary (the compiled code) itself. This is good news: you don't need to rebuild and re-upload your app.
Metadata includes everything in your App Store Connect listing:
- •App name, subtitle, and description
- •Screenshots and app preview videos
- •Keywords field
- •Privacy policy URL, support URL, marketing URL
- •App category and age rating
- •Demo account credentials (if your app requires login)
- •In-App Purchase descriptions and metadata
A Metadata Rejected status means one or more of these fields violated Apple's guidelines. The reviewer leaves a message in the Resolution Center explaining the specific issue.
Metadata Rejected vs Binary Rejected
The distinction matters because the fix is completely different:
Metadata Rejected:
- •Issue is in your listing information, not the code
- •Fix it directly in App Store Connect
- •No new build upload needed
- •Re-review is typically faster (metadata-only review)
- •Common causes: screenshot issues, missing demo account, URL problems, description violations
Binary Rejected:
- •Issue is in the compiled app itself
- •Requires code changes and a new build upload
- •New build must process before re-review
- •Re-review goes through the full queue again
- •Common causes: crashes, private API usage, missing account deletion, IAP issues
Metadata Rejected is the faster rejection to fix. You can often resubmit within minutes of reading the Resolution Center message.
Common Metadata Rejection Reasons
Screenshot Issues
Wrong sizes, non-Apple device frames, promotional text in screenshots, transparency in PNGs, or screenshots that don't reflect the actual app UI. The #1 metadata rejection cause.
Missing Demo Account
If your app requires login, you must provide demo account credentials in the App Review Information section. Missing this is an instant rejection.
Broken or Missing URLs
Privacy policy URL, support URL, or marketing URL must be live and accessible. 404 pages or placeholder URLs trigger rejection.
Description Violations
Keyword stuffing in the description, mentioning other platforms (Android), using 'beta' or 'test' language, or claiming features the app doesn't have.
Name or Subtitle Issues
App name or subtitle exceeding character limits, using other app names, or including pricing/promotional language.
Category Mismatch
App placed in a category that doesn't match its functionality, or missing required category-specific metadata.
Age Rating Inconsistency
Age rating questionnaire answers that don't match the app's actual content (e.g., unchecked 'unrestricted web access' when the app has a web browser).
Privacy Policy Issues
Privacy policy doesn't mention all required data collection, or the app collects data not disclosed in the policy.
How to Fix Metadata Rejection (Step by Step)
- 1.Read the Resolution Center message: Apple tells you exactly what's wrong. Don't guess — read their message first.
- 2.Identify the metadata field: the message references a specific field (screenshots, description, URLs, etc.)
- 3.Fix the issue in App Store Connect: edit the relevant field directly
- 4.Don't upload a new build: Metadata Rejected does not require a new build. Uploading one unnecessarily adds processing time.
- 5.Respond in the Resolution Center: acknowledge the fix and briefly explain what you changed
- 6.Resubmit: click 'Submit for Review' again. The metadata-only review is typically faster than a full review.
For screenshot issues specifically: export at exact App Store sizes, use Apple device frames only, remove any promotional text, and ensure no transparency. A screenshot tool that exports at correct sizes eliminates the most common metadata rejection.
How to Prevent Metadata Rejection
Pre-submission checklist to avoid metadata rejection:
- •Screenshots: correct sizes for all required device families, Apple devices only, no promotional text, no transparency
- •Demo account: provide credentials if your app requires login (username and password in App Review Information)
- •URLs: test all three URLs (privacy policy, support, marketing) in a browser — they must return 200, not 404
- •Description: no keyword stuffing, no platform mentions, no 'beta' language, no unverified claims
- •Name and subtitle: within character limits, no other app names, no pricing language
- •Age rating: complete the questionnaire accurately, especially web access and user-generated content
- •Privacy policy: covers all data your app actually collects, including third-party SDKs
- •Keywords: no other app names, no trademarks you don't own, within 100 characters
- •Category: matches app functionality
- •In-App Purchases: descriptions match actual IAP content, screenshots show real purchase screens
Run through this checklist before every submission. Most metadata rejections are preventable.
How Long Does the Re-Review Take?
After fixing metadata and resubmitting:
- •Metadata-only re-review: typically 12-24 hours (faster than full review)
- •The reviewer checks only the metadata you changed, not the entire app
- •If your fix doesn't address the issue, you may get rejected again with the same reason
- •Multiple metadata rejections for the same issue can slow future reviews: Apple may scrutinize your submissions more closely
The fastest path is to fix the issue correctly the first time. Read Apple's message carefully, fix exactly what they asked, and don't make unrelated changes that could trigger new issues.
Fix Screenshot Rejections for Good
Wrong screenshot sizes are the #1 metadata rejection cause. Export at exact App Store sizes, free, no sign-up.
Create Compliant Screenshots (Free)Related Articles
ASO Best Practices for 2026: The Complete Guide
The definitive guide to App Store Optimization in 2026. Learn the latest best practices for screenshots, keywords, localization, and conversion optimization.
ASO Trends to Watch in 2026
Stay ahead of the curve with the top ASO trends for 2026. Auto localization, dark mode, video-first listings, and more.
App Store vs Google Play: Screenshot Differences Explained
Learn the key differences between App Store and Google Play screenshot requirements, sizes, and best practices.