Xcode upload says no suitable application record was found
No suitable application records were found.Short answer
App Store Connect matches a build to an app record by the bundle ID and version inside the app bundle. If no record exists for that bundle ID, or you upload to a team that does not own it, the upload fails. Create the app record first, then make the bundle ID in Xcode match it exactly.
Fix it fast
1Find out which cause you have
Run a validation upload. It reads the bundle ID and version from the file itself, so what it reports is what App Store Connect sees. Compare that bundle ID with the one on your app record.
xcrun altool --validate-app -f MyApp.ipa -t ios -u you@example.com2Match what you see, then jump to its fix
- 1
The Apps page in App Store Connect has no app with your bundle IDNo app record exists yet in the account you upload toFix - 2
An app record exists, but with another bundle ID than the one in your buildThe bundle ID or version in the app differs from the recordFix - 3
You can see the app record, but uploads from your account failThe signed-in account's role cannot upload buildsFix
- 1
What does the error look like?
No suitable application records were found.
Cause 1 of 3
No app record exists yet in the account you upload to
1Check
Sign in to App Store Connect with the team you upload to and look through Apps. Apple states you can upload a build only after the app has been added to your account.
# In the browser: App Store Connect > Apps2Fix
Click the add button (+) in Apps and choose New App. Choose the platform and fill in the details, including the bundle ID. The Account Holder must have signed the latest agreement first, or you cannot add an app.
# In the browser: Apps > + > New App3Verify
The app appears in Apps with the status Prepare for Submission. Upload the build again.
xcrun altool --upload-app -f MyApp.ipa -t ios -u you@example.comConfirmed by developer.apple.com
Cause 2 of 3
The bundle ID or version in the app differs from the record
1Check
Apple says the bundle ID and version number stored inside the app bundle link the build to the app and version record. Open the target in Xcode, read the bundle identifier, and compare it character by character with the record.
# In Xcode: target > General > Identity > Bundle Identifier2Fix
Change the bundle identifier in the Xcode target to the one on the record. Do this for every build configuration that you archive.
# Xcode: set Bundle Identifier = com.example.myapp, then Product > Archive3Verify
The validation run accepts the build.
xcrun altool --validate-app -f MyApp.ipa -t ios -u you@example.comConfirmed by developer.apple.com
Cause 3 of 3
The signed-in account's role cannot upload builds
1Check
Open Users and Access and read your role. Apple lists the Account Holder, Admin, App Manager and Developer roles as the ones that can upload builds.
# In the browser: Users and Access > People > your name > Roles2Fix
Upload with an account that has one of those roles, or ask the Account Holder or an Admin to change your role.
# Done in Users and Access by the Account Holder or an Admin3Verify
The upload completes and the build processes. Apple sends an email once processing finishes.
# Check your email and the TestFlight tab for the new buildConfirmed by developer.apple.com
How do I stop it coming back?
- Create the app record in App Store Connect before the first archive, and copy its bundle ID into Xcode.
- Keep one bundle ID per app in a build setting, so debug and release targets cannot drift.
- Check which team and account Xcode signs in with before you upload.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.
Which stack is behind this page?
Related fixes
Mobile apps
App record creation fails because you lack permission
You cannot add a new app in App Store Connect as a Developer or limited user
Only the Account Holder, an Admin or an App Manager can create an app record, and Apple blocks it until the Account Holder has signed the latest agreement.
3 causes, each with a fixMobile apps
Cannot change the App Privacy answers in App Store Connect
Publish Your App Privacy Responses?
Only the Account Holder, Admin and App Manager roles can answer the App Privacy questions.
2 causes, each with a fixMobile apps
You cannot find the button to pull your app back from review
No 'remove this version from review' message appears on the version page
There is no button called Reject Binary.
3 causes, each with a fixMobile apps
Your Apple Account cannot sign in to App Store Connect
Sign-in to App Store Connect is refused for an account that should have access
App Store Connect does not open to every Apple Account.
3 causes, each with a fixMobile apps
Apple rejected the app under Guideline 4.3, Design: Spam
Guideline 4.3(b) - Design - Spam
Guideline 4.3 is Apple's duplicate rule.
5 causes, each with a fixMobile apps
App Store Connect rejects a screenshot because it has transparency
Images can't include alpha channels or transparencies.
App Store Connect does not accept screenshots that carry an alpha channel or transparent pixels.
2 causes, each with a fix