App Store Connect setup guide
Treat App Store Connect as a release system, not a last-minute upload screen.
A clean iOS launch needs Apple Developer ownership, an app record, bundle ID alignment, build upload, metadata, screenshots, privacy details, TestFlight, App Review notes, and a handover that the owner can maintain.
Searching for App Store Connect usually means the app is close to launch but the release workflow is not yet organized. The code may be done, but App Store Connect setup still decides whether the submission is easy to review, easy to maintain, and easy to hand over.
Official source note: Apple says you create an app record in App Store Connect before uploading a build, and the record is where platform-specific information is managed: Add a new app.
The App Store Connect path
New App Store launch
Start with Apple Developer ownership, bundle identifier, app record, signing, metadata, privacy details, TestFlight, and reviewer notes.
App Review or TestFlight issue
Recheck crashes, login access, app privacy details, metadata claims, payment flows, permission prompts, and the exact App Review message.
Flutter or React Native release
Treat the iOS release as a native Apple workflow: Xcode signing, build numbers, App Store Connect upload, TestFlight, and review handover.
Quick answer
App Store Connect setup should be run as a controlled launch checklist.
For a new iOS app, prepare:
- Apple Developer account ownership and App Store Connect roles.
- Bundle ID, app services, signing path, and build number convention.
- App Store Connect app record: platform, name, primary language, bundle ID, and SKU.
- Store metadata: app name, subtitle, description, keywords, support URL, marketing URL, category, and contact details.
- Screenshots and app previews that match the actual product.
- App Privacy details based on the real app and SDK behavior.
- TestFlight setup, reviewer notes, demo credentials, and release notes.
- A handover document covering owner access, signing, build upload, metadata, privacy answers, release status, and support contacts.
Quick answer: App Store Connect setup checklist
Confirm who owns the Apple Developer membership, who can manage App Store Connect, and who can submit releases.
Create the App Store Connect record only after the app name, platform, bundle ID, primary language, and SKU convention are clear.
Make sure the Xcode archive, version, build number, signing, entitlements, and upload path are ready before metadata review.
Prepare app copy, screenshots, privacy answers, age rating, reviewer access, and support URLs from the real product.
Test through TestFlight, submit to App Review, respond to issues, release deliberately, and document the handover.
Phase 1: confirm owner and team access
The most important App Store Connect setup decision is ownership. A founder, company, or product owner should understand who controls the Apple Developer team and who has App Store Connect permissions.
If a contractor owns the Apple Developer team, the business can become dependent on that contractor for certificates, API keys, TestFlight, review responses, agreements, tax details, and future releases. The durable setup is usually business-owned membership with agency or developer access granted through roles.
Account ownership checklist
- Confirm the Account Holder and long-term owner.
- Check whether the app should be under an individual or organization membership.
- Add team members only with the permissions they need.
- Keep recovery methods with the business owner.
- Document who can manage users, upload builds, edit metadata, submit to review, and release.
- Confirm whether paid apps, subscriptions, in-app purchases, or banking agreements are in scope.
Phase 2: create the app record carefully
The app record connects the public listing, platform information, bundle ID, metadata, builds, TestFlight, pricing, availability, and review submissions. Create it only when the identity basics are stable.
App record worksheet
| Item | What to decide | Why it matters |
|---|---|---|
| Platform | iOS, iPadOS, or other Apple platform scope | Controls the submission surface and required assets |
| Name | Public app name | Needs product-owner approval before assets are created |
| Primary language | Default listing language | Sets the baseline for metadata and localization |
| Bundle ID | The exact app identifier | Must match the app build and signing setup |
| SKU | Internal unique identifier | Helps operations and future reporting |
| Owner | Business or product owner | Avoids future access dependency |
Phase 3: align build, signing, and upload readiness
The App Store Connect record does not fix an unready iOS build. Before submission day, confirm that the release build uses the correct bundle ID, version string, build number, capabilities, icons, permission strings, production endpoints, and signing method.
Make it final before upload
Bundle ID mistakes create avoidable release friction. Confirm the identifier with the developer, owner, and any backend integrations before the app record is used.
Know who controls certificates
Automatic signing may be enough for many teams, but the owner should still know which Apple team, certificate path, and Xcode account are used for releases.
Increment every upload
Every uploaded build needs a clean version and build-number rhythm. Document it so hotfixes do not become confused later.
Test production behavior
The release build should point to production-safe services, use correct push notification setup, and hide staging-only diagnostics.
Phase 4: prepare metadata, privacy, and screenshots
App Store metadata should describe the real product. Do not overpromise. Do not show screenshots of features that are not available. The app description, screenshots, privacy answers, permission prompts, support URL, marketing claims, and reviewer notes should all tell the same story.
Metadata readiness checklist
- App name, subtitle, description, keywords, category, and age rating are reviewed.
- Support URL and privacy policy URL are live and owned by the business.
- Screenshots show actual app screens and important workflows.
- App Privacy details are answered from the real data and SDK inventory.
- Reviewer notes explain restricted access, demo credentials, paid features, hardware needs, or region-specific behavior.
- Contact details route to someone who can answer review or support questions.
Phase 5: TestFlight, review, and release handover
TestFlight is where the owner, QA, client, and developers should catch release issues before App Review. After testing, use App Store Connect to submit the selected build and related items for App Review. Apple controls the review decision, so the practical goal is review readiness, not a guarantee.
Upload and process the build
Upload the signed build through the agreed path, wait for processing, and confirm warnings before assigning it to TestFlight or a version.
Run TestFlight with real flows
Test login, onboarding, push notifications, payments, account creation, deletion, permissions, deep links, and support routes.
Submit with reviewer notes
Include demo credentials, step-by-step access instructions, known limitations, and any context the reviewer needs to test the app.
Document handover
Hand over app record details, roles, signing notes, build archive details, metadata source files, privacy answers, release status, and support contacts.
Common setup mistakes
Creating the app under the wrong owner
App Store Connect access problems often appear later during updates, rejection responses, or team changes. Decide ownership before the record is created.
Treating privacy as a marketing task
App Privacy details need input from the actual app, backend, analytics, crash reporting, ads, payments, and third-party SDKs.
Submitting without reviewer access
If the reviewer cannot log in, reach restricted features, or understand a paid flow, the review can slow down for reasons unrelated to code quality.
No release handover
Future updates become risky when only one developer knows the signing setup, build number convention, metadata source, and review history.
FAQ
What do I need before creating an app in App Store Connect?
You need Apple Developer account access, a final app name decision, primary language, bundle ID, SKU convention, team ownership, support contacts, and a release-ready plan for metadata, screenshots, privacy details, and review information.
Can Shinka guarantee App Store approval?
No. Apple controls App Review outcomes. Shinka can prepare the account, app record, signing checks, metadata, privacy details, TestFlight flow, reviewer notes, and response plan to reduce avoidable submission issues.
Should an agency own the App Store Connect app record?
Usually the long-term business owner should control the Apple Developer team and App Store Connect app. Agencies can be added with scoped roles and removed or reduced after handover.
