Fix submission errors
Resolve the most common build, metadata, privacy, and review-state blockers.
A submission error usually belongs to one of four layers: the Apple account, the app identity, the uploaded build, or the App Store Connect record. Read the exact message before changing anything.
Apple agreements or account access are blocking publishing
Sign in to Apple Developer and App Store Connect as the Account Holder. Accept pending agreements, confirm the membership is active, then reconnect the correct team in Superapp.
The bundle identifier or app record does not match
Confirm that the bundle identifier in Superapp is identical to the identifier owned by the selected Apple team and attached to the intended App Store Connect app. Do not create a second record to work around a typo.
The build uploaded but is not available
Apple must process each upload. Wait for the exact build number, then check for an email from Apple describing a processing failure. Upload a new build only after resolving that reason.
App Privacy is not published
Open the app’s App Privacy section in App Store Connect, complete the data-use questionnaire, and click Publish. Saving answers without publishing them is not enough.
What's New is required
Every update after the first release needs release notes. Add a concise description of user-visible improvements and fixes, then submit again; the existing upload can remain.
The App Store version is locked
A version already used for a completed review cannot accept a different release. In Superapp, bump to the suggested marketing version, rebuild, and upload the fresh build.
The submission has unresolved review issues
Read Apple’s message in App Store Connect. Reply if the reviewer needs information, or withdraw the open submission before submitting a different version. Withdrawing does not delete the app or its metadata.
Signing or entitlements fail
Verify the selected team, bundle identifier, certificates, and capabilities. A feature such as push notifications, Sign in with Apple, HealthKit, or associated domains must be enabled consistently for the identifier and the build.
Required metadata is missing
Complete every highlighted field, including category, description, keywords, pricing, reviewer contact details, support URL, privacy URL, and demo credentials when sign-in is required.
When you ask for help
Copy the complete error, name the publishing step, and include the marketing version and build number. Never send your Apple password, verification code, private key, or signing certificate.