How to publish an iPhone app to the App Store
Everything between a working iPhone app and the App Store. What you need from Apple, the checks to run before you submit, the three-step Publish flow in OpenV2, what happens in App Store Connect, and how to handle a rejection.
By the OpenV2 team
Your app works in the simulator and on your phone. The last step looks like one button, but it is really three things: an Apple account that is allowed to publish, a build that Apple accepts, and a listing and review that Apple approves. This guide walks through each one, using OpenV2's Publish flow.
Before you start: what Apple requires
| You need | Why |
|---|---|
| An Apple Developer Program membership | Only members can distribute on the App Store or TestFlight. Apple sets the annual fee. |
| Access to App Store Connect | Where the listing, screenshots, privacy details, TestFlight and review live |
| A successful iOS build | The binary that gets uploaded |
| A Pro or Max plan on OpenV2 | Publishing is part of the paid plans |
A free Apple account is enough to test on your own iPhone, but not to publish. If you are still testing, see how to build and test an iPhone app without a Mac.
Step 1: get the app ready for review
Most rejections are predictable. Before you submit, type / in the chat and choose Ready for the App Store. The agent checks common review problems and prepares listing text:
- Permissions and their descriptions. If the app uses the camera, location, photos or notifications, each permission needs a clear reason shown to the user.
- Placeholder content. Lorem ipsum, test buttons and empty screens are a classic rejection.
- Login requirements. If part of the app needs an account, the reviewer needs a way in.
- Listing text such as the description and keywords.
The App Store section of your project also shows a review check.
Then check the app's identity, which you cannot change easily after the first release:
- the display name,
- the bundle identifier,
- the version and build number,
- the app icon.
Step 2: the three-step Publish flow
Press Publish and choose App Store (or open More → App Store).
| Step | What you do |
|---|---|
| App Info | Confirm the name, bundle identifier, version and icon |
| Apple Developer | Sign in, pick the account that has the membership, and complete Apple's verification |
| Submit | Follow the build and upload progress, and fix any reported error |
Complete Apple's two-factor verification when it appears, and keep the wizard open while it works. OpenV2 builds the release and uploads it to App Store Connect.
Step 3: finish in App Store Connect
An upload is not an approval. After the upload, App Store Connect is where you:
- Test with TestFlight, if you want testers to try the build first.
- Complete the listing: screenshots, description, category, support link.
- Fill in the privacy details: what data the app collects and why.
- Submit for review.
Apple decides when the app is reviewed and when it is released. Make sure the listing matches what the app really does: screenshots of features that do not exist are a common problem.
If something fails
| Problem | What to do |
|---|---|
| Verification fails | Repeat the Apple sign-in and the two-factor code |
| The build is rejected on upload | Read the error, ask the agent to fix it and submit again |
| The wrong account is selected | Go back a step and pick the account that has the membership |
| App Review rejects the app | Send the rejection text to the agent: it can fix the reasons |
The last row is worth repeating: paste Apple's rejection message into the chat. It usually names the guideline and the screen, which is exactly what the agent needs to fix it.
A checklist you can copy
- Apple Developer Program membership active
- Ready for the App Store check run, issues fixed
- Every permission has a clear description
- No placeholder text or test screens
- Reviewer can sign in (or no sign-in is needed)
- Name, bundle identifier, version and icon confirmed
- Upload finished in the Publish flow
- Listing, screenshots and privacy details done in App Store Connect
- Submitted for review
Publishing to Android too
The same app idea can ship on Google Play. OpenV2 writes a separate native Android app in Kotlin and has its own Google Play flow. See how to publish an Android app to Google Play.
Frequently asked questions
Do I need a Mac to publish to the App Store?
Not with OpenV2. The release build and the upload to App Store Connect run in the cloud. You need an Apple Developer Program membership and App Store Connect access.
How long does App Store review take?
Apple decides when an app is reviewed and released, and the timing varies. OpenV2 uploads the build; review and release stay with Apple.
What happens if Apple rejects my app?
Read the rejection message, paste it into the OpenV2 chat and ask the agent to fix the reasons. Then submit again.
Can I publish on the Free plan?
No. Publishing to the App Store needs a Pro or Max plan, plus an Apple Developer Program membership. On Free you can build, use the simulator within the trial and install on your own phone.
