What You Prepare
| Item | Notes |
|---|---|
| App name (30 characters max) | Short and memorable, include a keyword if natural |
| Subtitle (30 characters) | One line benefit |
| Description | First lines matter most. Explain value, not just features |
| Keywords (100 characters) | Comma-separated, no spaces, do not repeat words from the name |
| Screenshots | Required sizes for the largest iPhone (and iPad if supported). Show real app screens with short captions |
| App icon | 1024 x 1024 px, no transparency |
| Privacy Policy URL | A public web page, required |
| Support URL | A page or email form for users |
| Category and age rating | Answer the questionnaire honestly |
Privacy Details
Apple shows App Privacy labels. You declare which data your app collects (email, location, usage data, identifiers) and whether it is linked to the user or used for tracking. Include the data collected by any third-party SDK, such as analytics or ads.
- If you track users across other companies' apps and sites, you must ask permission with the App Tracking Transparency prompt
- Apps that let users create accounts must also let them delete the account from inside the app
- Add a privacy policy that matches what the app really does
Submission Steps
- Upload a build (previous lesson) and wait until it is processed.
- Open your app in App Store Connect and create a new version.
- Fill in the listing text, keywords and screenshots.
- Select the build.
- Add App Review Information: contact details and, if your app needs a login, a demo account that works.
- Choose the release option: manual, automatic or scheduled.
- Click Submit for Review.
Common Rejection Reasons
| Reason | How to avoid it |
|---|---|
| Crashes or bugs | Test on real devices with the Release build, use TestFlight |
| Incomplete app or placeholder content | Remove 'lorem ipsum', dead buttons and broken links |
| Login without a demo account | Give reviewers working credentials in the review notes |
| Unclear permission texts | Explain the user benefit |
| Misleading metadata | Screenshots and description must match the real app |
| Minimum functionality | A simple website wrapper is not enough. Offer real app value |
| In-app purchases not used correctly | Digital content and subscriptions must use Apple's In-App Purchase system |
| Missing account deletion or privacy policy | Add both before submitting |
If you are rejected, read the message in Resolution Center, fix the issue and reply or resubmit. Rejections are normal, even for experienced developers.
After Release
- Watch crashes and feedback in App Store Connect > Analytics and Xcode Organizer
- Answer reviews
- Ship updates with a higher version or build number and What's New text
- Use phased release for updates, so a bug does not reach everyone at once
Conclusion
A strong listing, honest privacy answers, a working demo account and a stable build lead to a smooth review. Expect to learn from a first rejection.

