Fix: No suitable application records were found in Xcode

Fix: No suitable application records were found in Xcode
Quick answer: Make sure the app target’s bundle identifier exactly matches the Bundle ID on its App Store Connect record, including capitalization. If there is no matching app record, create one in App Store Connect, then archive and upload the app again.

Why this happens

Xcode displays No suitable application records were found. Verify your bundle identifier is correct. when it cannot find an App Store Connect app record that matches the app being uploaded.

One cause is a difference in capitalization: for example, the record may use com.example.MyApp while the Xcode target uses com.example.myapp. The identifiers look similar, but changing the Xcode value to match the record resolved the error in the reported case.

The error can also occur if you registered a bundle ID but have not created an app record for it in App Store Connect. The registered identifier and the App Store Connect app record are related, but creating one does not automatically create the other.

How to fix it

1. Match the bundle identifier exactly

Start with the existing App Store Connect record. This is especially important when you are uploading a new version of an existing app: use that app’s identifier rather than making up a new one.

  1. Sign in to App Store Connect and open Apps.
  2. Select the app you intend to upload.
  3. Open App Information and find its Bundle ID.
  4. In Xcode, select your project in the project navigator, then select the app target.
  5. Open the General tab and find Bundle Identifier under Identity.
  6. Compare the two values character by character, including uppercase and lowercase letters.

For example, if App Store Connect shows com.example.MyApp, set the Xcode target to that exact value, not com.example.myapp. The example is only a placeholder; use the identifier on your own record.

After correcting the setting, create a new archive and upload that archive. Changing the project setting does not alter an archive you already created.

If the General tab’s value is controlled by build settings or a configuration file, make the correction at the source of that setting. The value that matters for upload is the identifier in the archived app, not just a value you intended to use.

2. Create an App Store Connect app record

If the identifier matches your Xcode target but there is no corresponding app in App Store Connect, create the record before uploading.

  1. Sign in to App Store Connect with access to the intended organization.
  2. Open Apps, use the add button, and choose New App.
  3. Enter the requested app information and select the bundle ID that matches your Xcode app target.
  4. Create the record, then return to Xcode and upload a new archive.

If the bundle ID you need is not available to select, check that it has been registered for the intended developer team and that you are working in the right organization. Avoid creating a second app record if the correct one already exists; first check whether you are viewing the right account and app.

An app being in Prepare for Submission does not by itself explain this particular error. Check the identifier and the existence of the matching record instead of relying on how long the app has been in that state.

3. Check the identifier inside the archive

If the settings appear correct but upload still fails, inspect the archive you actually selected for distribution. This helps identify an old archive or a different value used by the archive’s build configuration.

In Xcode’s Organizer, locate the archive and use Show in Finder. In Finder, open the archive’s package contents and locate the app under Products/Applications. Its Info.plist contains CFBundleIdentifier.

You can also print the value in Terminal. Replace the example path and app name with the ones from your archive:

/usr/libexec/PlistBuddy -c 'Print :CFBundleIdentifier' \
  '/path/to/MyApp.xcarchive/Products/Applications/MyApp.app/Info.plist'

Compare the output with the Bundle ID in App Store Connect. If it differs, check the app target’s Build Settings for PRODUCT_BUNDLE_IDENTIFIER, including any configuration-specific values. Also check which build configuration the scheme uses for Archive. Correct the value, archive again, and inspect the new archive before uploading it.

Make sure you inspect the main app’s Info.plist, rather than the plist for an extension or another embedded product. You can have several targets in one project, each with its own bundle identifier.

4. Verify the account and team

If the archived identifier is an exact match, confirm that Xcode and App Store Connect are using the intended developer organization. A matching app record in a different organization will not help an upload to the wrong one.

In Xcode, check the app target’s Signing & Capabilities settings and the team selected for the target. In App Store Connect, verify that you can open the intended app record under the corresponding organization. Then retry distribution with the appropriate account and team.

If access to the app or organization is missing, ask an account administrator to check your access rather than changing the bundle identifier to an unrelated one.

How to prevent it

  • Copy the Bundle ID from the app record when configuring the Xcode target, and preserve its capitalization.
  • Create the App Store Connect record before the first upload.
  • Check configuration-specific bundle IDs when a project has separate development and release settings.
  • Label or inspect archives when working with multiple apps, schemes, or teams, so you upload the intended build.

FAQ

Does a matching app name fix this error?

No. The displayed app name is not a substitute for the bundle identifier. Compare the identifier in the archived app with the Bundle ID on the App Store Connect record.

Do I need to wait for Prepare for Submission to finish?

Not to address this error. First verify that the app record exists and that its Bundle ID matches the archive exactly. The reported issue was resolved by correcting capitalization, not by waiting.

Can I reuse the archive after changing the bundle ID?

No. An existing archive contains the app built with its earlier settings. Create and upload a new archive after making the correction.

Sources & credits

Parts of this guide are adapted from content licensed under CC BY-SA 4.0; this article is shared under the same license.