Digital reference
How to Publish an iPhone App on the App Store: Steps and Common Fixes
What must you finish before publishing an iPhone app?
Enroll in the appropriate Apple Developer Program account, create an App Store Connect app record before uploading a build, supply accurate metadata and required declarations, test the signed build, select it for App Review, then submit and manage the release. An uploaded build or 'Ready for Review' status alone does not mean your app has been submitted or published.
Publishing stages and how to unblock them
| Stage | What to do | Common issue and next check |
|---|---|---|
| Account | Confirm program membership, agreements and the correct account type | New App disabled: check Account Holder agreements and permissions |
| App record | Create the name, primary language, bundle ID and SKU | App not accepting build: confirm bundle ID and platform |
| Build | Upload a correctly signed build and wait for processing | Build missing: inspect processing and delivery messages |
| Store page | Add accurate text, screenshots, privacy disclosures, rating and availability | Missing information: resolve validation fields; do not invent screenshots |
| Review | Select the build, Add for Review, then Submit for Review | Ready for Review is not the same as In Review |
| Release | Set pricing, regions and automatic/manual release preference | Approved but not live: check release settings and storefront availability |
TestFlight versus App Review
TestFlight is for beta testing and collecting feedback, not the same as public App Store review. TestFlight builds expire after 90 days and first external beta builds may undergo beta review; there is no general Apple rule demanding 12 testers for 14 days.
- Test login, purchases and restore if relevant.
- Provide working reviewer access and honest notes.
- Check crashes, missing content and permission prompts on devices.
Why does Add for Review not publish the app?
Apple separates adding the item to a draft submission from actually selecting Submit for Review. The submission then moves through waiting/review states. Review completion and public availability also depend on the selected release option.
What if Apple rejects the submission?
Open the App Review message, identify the exact guideline, reproduce the issue, resolve it and reply with concise evidence. Metadata-only problems may allow resubmitting the existing build; issues requiring functionality changes need a corrected build. Never blindly resubmit unchanged after a design/spam rejection.
App Store ASO and localization checks
Apple limits the app name and subtitle to 30 characters each, and the localized keyword field to 100 bytes. Descriptions may use up to 4,000 characters. Choose accurate intent-driven terms, real screenshots, localized copy and working support/privacy URLs; do not repeat a competing brand name or promise features not in the build.
Does App Store publication require D-U-N-S or 12 testers?
Apple organization enrollment normally requires a D-U-N-S number and legal-entity verification; Apple individual enrollment has different requirements. The 12-testers/14-days closed-test gate belongs to certain Google Play personal developer accounts, not to Apple App Store submissions.
Related tools and guides
Official Apple sources
Guidance checked:
- Apple — App Store Connect workflow
- Apple — Add a new app
- Apple — Submit an app
- Apple — Store metadata field requirements
- Apple — App name and subtitle limits
- Apple — App Review messages
This independent reference is not official Apple/Google support. Account type, region and platform rules vary; verify current Console requirements. No review or publication approval is guaranteed.