Recommended Free Tools
Most App Store submission problems are fixable once you identify whether the issue is an incomplete submission, a review-access or app-completeness problem, inaccurate listing information, or a specific policy concern. In App Store Connect, follow the status and message Apple gives you: “Ready for Review” means the item has not yet been sent to Apple, and a metadata-only rejection may be corrected and resubmitted with the same build.
Why was my app rejected or not sent for review?
These problems can look alike in App Store Connect but require different actions. First check the status, then read any message attached to the item. Apple’s status definitions distinguish a submission that is still waiting to be sent from one Apple has rejected.
- Ready for Review: the item has been added to a submission, but it has not been sent to Apple.
- Waiting for Review: Apple has received the submission, but review has not started.
- In Review: Apple is reviewing it.
- Rejected: Apple did not accept the item. Check the rejection message for the cited guideline or other issue, then correct and resubmit or remove the item from the submission.
Apple says that, on average, more than 40% of unresolved issues relate to Guideline 2.1, App Completeness. That is Apple’s broad characterization of unresolved issues, not a diagnosis of any particular rejection. Apple also says that, on average, 90% of submissions are reviewed in under 24 hours; this is not a guaranteed turnaround time for an individual submission. See Apple’s App Review guidance.
How do I make sure the submission was actually sent?
Submitting an app version involves two distinct actions: add the version to a submission, then explicitly send that submission for review. Apple instructs developers to provide required metadata and choose the build before submitting an app version for review. Use this sequence in App Store Connect:
#1 Best Overall
- Used Book in Good Condition
- Complete the required app-version metadata and select the intended build.
- Review the version details and confirm that the correct build is attached.
- Select Add for Review to add the version to a new or existing submission. This changes the status to Ready for Review; it does not start review.
- Open the submission and select Submit for Review to send it to Apple.
Apple’s step-by-step directions are in Submit an app. For a new release, do not assume that selecting a build or seeing “Ready for Review” means Apple has received it.
When a submission contains more than one item
A submission can include an app version and, where supported, other items such as in-app purchases, subscriptions, events, custom product pages, product page optimization tests, or Apple-hosted asset packs. Items may be reviewed together, and Apple says every item in a submission must be accepted for that submission to be complete. Platforms are generally managed and submitted separately; an item’s status on one platform does not establish the status of another. See Apple’s overview of submitting for review.
Fix common causes before submitting
Apple’s App Review checklist highlights issues that can prevent a smooth review. Check the relevant area rather than making unrelated changes.
Crashes, bugs, and unfinished features
Test the important app flows on supported devices and current software, especially launch, account creation or sign-in, and the features highlighted in your listing. Fix reproducible crashes and defects. Remove placeholder screens, unfinished copy, and incomplete content. Apple treats crashes, bugs, and incomplete experiences under App Completeness (Guideline 2.1).
Broken links and unreachable contact details
Open every link in the reviewed build. Verify that the user support link works and provides current contact information, and that the privacy policy link resolves. Make sure the contact details are monitored so the reviewer can reach someone if needed.
Missing credentials or setup instructions
If the app requires sign-in, enter valid demo credentials in App Review Information and confirm they work. Explain any special configuration needed to reach the features under review. For functionality that depends on difficult-to-replicate conditions, specific hardware, or an unusual environment, Apple advises providing a demo video or the required hardware. Keep the review contact information complete and current.
Unclear permission prompts or data use
Explain clearly why the app requests access to user or usage data, and give a concrete example where that helps the reviewer understand the purpose. If the app references APIs that access sensitive user data, include an Info.plist purpose string that explains the need in user-facing language. The explanation and prompt should accurately describe what the app does.
Inaccurate screenshots or listing details
Use screenshots that show the app’s actual functionality and value. Do not obscure the interface, and match each screenshot to its corresponding device type. Apple’s screenshot guidance requires at least one screenshot and permits up to ten for each device size. Its current reference calls for at least one iPhone screenshot for an iPhone with Dynamic Island (medium display), and at least one 13-inch iPad screenshot if the app supports iPadOS. If the interface and localizations are consistent across sizes, Apple says the highest required resolution can be supplied and scaled down. Check Apple’s live screenshot specifications and upload instructions when preparing assets, because requirements can change.
Free tools Windows power users keep installed
One-click scans. No signup required.
Check metadata field limits as well. Apple’s current app information reference sets the app name at 2–30 characters and the subtitle at a maximum of 30 characters, and provides a privacy policy URL field. See App information rather than relying on older third-party checklists.
Rank #4
- Used Book in Good Condition
How to respond to an App Review rejection
Use the rejection message as the diagnosis. It identifies the guideline or issue Apple believes applies; the remedy depends on what the notice says. Apple’s instructions are in Reply to App Review messages.
- Open the rejected item in App Store Connect and read the full message, including the guideline cited and any requested information.
- In the App Review section, reply directly to the concern. Explain what you changed or clarify how the existing behavior meets the stated requirement.
- Attach supporting material when it helps explain the correction, such as relevant steps or a demonstration of a feature.
- Make the change the notice calls for. A metadata-only issue can be fixed and resubmitted using the same build. For a functional or policy issue, determine from the notice whether code, content, settings, or additional review information must change.
- Resubmit the item and verify its new status in App Store Connect.
Accepted items can remain unpublished while other items in the same submission are rejected. If that happens, address the rejected item and consult the submission status rather than assuming all items share one outcome.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
