Reputation: 3196

No suitable records were found verify your bundle identifier is correct

I have created an app in App Store Connect and it has been in the "prepare for submission" state for more than 3 days. When I try to archive my app, and submit it to the app store it, displays this message:

No suitable application records were found. Verify your bundle identifier is correct.

Upvotes: 171

Answers (30)

Amr

Reputation: 653

For me, I did all this but doesn't solve the problem so all I had to do is to assign the right bundle on the apple store connect ( the bundle id that is already exist in the IPA file )

Upvotes: 1

Ragul

Reputation: 3196

Just found the Error. I used one capital letter in bundle id. but I have used small letters in Xcode's bundle id. now I changed that as like in the app id. and now I successfully uploaded my app to Appstore Connect.

Upvotes: 72

vhiktordom

Reputation: 173

If you tried all the above and it did not work for you simply ensure the Identifier name matches with that of your app name.

Example: Let's say my identifier name is VictorDominic and my identifier is com.company.victordominic your app name should be VictorDominic if not you will get the above error.

Please take note of the casing. If your identifier name is Victordominic and your app name is VictorDominic you will still get this error.

Upvotes: 0

Krister Berntsen

Reputation: 173

Had this happen to me and my case was an odd one.

I had multiple accounts added in Xcode, but only when i added my private account to the job-team in addition to the job-account, i encountered problems.

Turns out that xcode somehow checked for permissions with my private accounts who only had a customer-support role and not a developer role. It completely ignored my work-account that had the developer role.

Solution was to remove the account which lacked permissions, so that xcode used the proper account.

Upvotes: 1

Gaurav Taywade

Reputation: 8347

Just check that app you configured on iTuneconnect is having same bundle identifier that you are using to upload app.

URL: https://appstoreconnect.apple.com/apps

Upvotes: 50

VinothV

Reputation: 169

First login your developer account.
Check your bundle identiifer correctly
Then Check in your app store connect the new app is create or not as the same bundle identifier (is the main error)
Choose your correct bundle identifier to create new app.
Now you upload your app it get success.

Upvotes: 0

Ian

Reputation: 2640

I got the error when uploading a React Native Expo bundle to Apple App Store Connect using Transporter. The problem was that I had transferred the app from my personal account to our company account but forgot to sign into our company account in Transporter.

Click the profile icon in the top right corner and sign in to the correct account that you are using in your bundle.

Upvotes: 1

Emre Gürses

Reputation: 2180

if your app transfer other account. You should rearrange Signing section for the corrcet team(new team)

Upvotes: 0

msalihbindak

Reputation: 622

After few days I realize that, I've set Bundle ID wrong.

Here is how I correct,

Go App Store Connect > Your App > App Information > General Information

Select the Bundle ID you create and assign at xcode before.

Now you can Upload without error.

Upvotes: 3

Igor Kharakhordin

Reputation: 9933

In my case, I had 2 Apple IDs in my Xcode preferences (Xcode -> Preferences -> Accounts), so I had to remove one. After I removed Apple ID that I didn't need, validation process worked just fine.

Wasted a few hours, just because the error message is useless. This is so frustrating.

Upvotes: 9

Daniel Danielecki

Reputation: 10590

When changed a project name from HelloCordova to that one I wanted I encouraged this problem. Even though in PROJECT_NAME -> General -> Bundle Identifier as well as in PROJECT_NAME -> Build Settings -> Product Bundle Identifier I changed it as it should be still had the same error. What solved the problem was simply to open a different editor and look for this string PRODUCT_BUNDLE_IDENTIFIER and changed all the names I don't want to the correct ones. Apparently Xcode takes the bundle identifier also from somewhere else than these 2 locations.

Upvotes: 1

Aus_10

Reputation: 780

Since this is question obviously has different potential answers depending on the individual circumstances I thought I'd add my problem and what solved it:

Problem: I had someone copy the binary archive, make some changes and then pass the binary onto me. This caused a binary conflict.

Solution: I had to create a new certificate. I copied the bundle ID from the develop consul, pasted into xcode and was able to upload.

Side note: You can regenerate a new bundle id by turning on "In-App Purchases" under Capabilities.

Upvotes: 3

gafi

Reputation: 12804

For me, it was because I forgot to create a "Provisioning Profile" on Apple developer portal. I created a profile here for "App Store", then downloaded and opened the file and it worked!

Upvotes: 2

Luke Redmore

Reputation: 449

Make sure this is included in your Info.plist:

<key>CFBundlePackageType</key>
<string>APPL</string>

I had APPL misspelled as AAPL. Once I fixed that and signed into Application Loader and Xcode with the same Apple ID, everything worked.

Upvotes: 3

Gowtham

Reputation: 486

I've changed the Version number but forgot to change the Build version. Changing the Build version resolved the issue. Such a silly mistake. Smh...

Upvotes: 3

Zaim Ramlan

Reputation: 591

What did the fix for me is to allow app access to all users:

Go to AppStore Connect
Go to My App
Under Additional Information, click on 'Edit User Access'
Select 'Full Access'
This allowed me to upload the app the first time (via Xcode & Application Loader)

After the initial upload, i can switch back to 'Limited Access' and upload just fine.

Upvotes: 25

Daniel Storm

Reputation: 18898

If after you confirm your Bundle ID's match across App Store Connect, Apple Developer Portal, and Xcode and you are still having issues try this:

Remove the Apple ID associated with the Bundle ID you're experiencing issues with from your Accounts list in Xcode (Menu Bar -> Xcode -> Preferences -> Accounts). Then, add the Apple ID back to the Accounts list in Xcode.

Upvotes: 2

vinod neeloju

Reputation: 45

Check Requires full screen is enabled or not. If not enable it.

You can find that option in the below steps.

Targets -> General -> Deployment Info -> Requires full screen.

Upvotes: -1

Roger Perez

Reputation: 3139

iTunes Connect || App Store Connect (website):

In your browser, go to iTunes connect/ App Store Connect.

Add your New App / edit your existing app.
Go to App information.
Check the Bundle ID name.
If there is no bundle ID, make sure you create one.
I used the WildCard bundle ID. That means, your complete bundle ID is likely to be com.organizationName.* and the suffix (exampleApp). Xcode:
Go to your Workspace / Project.
Go to your project.
Select the General Tab.

Ensure the Bundle Identifier is the name you set in iTunes Connect.

For example: com.orgnanizationName.appName

It seems you have to start the App Store submission process in iTunesConnect.

Upvotes: 32

vinod neeloju

Reputation: 45

Once check this.

Open your .plist file and check for "Bundle OS Type code" key. If that is not there, add a row and give that key and check the type it should be a string. And give "APPL" as value.

Clean the project and go for Archive.

I hope it will work for you.

Upvotes: 3

Siempay

Reputation: 1002

For me : Just tried uploading using Application Loader and it worked

Upvotes: 2

Baran

Reputation: 2820

iMessage Extension: For everyone that is fighting with this problem with an messages extension (or any other extension) make sure you enter in "App Store Connect" -> "General Information" -> the Bundle-ID of the application target and not the extension target. We fought 2 days to find this out.

Upvotes: 2

Ammar Mujeeb

Reputation: 1321

I have to manually sign the app. Created new certificate and new profile. Set code signing to Manual. Only then i was able to upload. Moreover select Manual sign in from organizer while uploading build.

Upvotes: 3

Luat Vu Dinh

Reputation: 480

Using Application Loader worked in my case.

Upvotes: 5

Jacky Chong

Reputation: 172

In my case

Checked if same user in itunes and xcode
Checked bundle ID is same

Solution:

Go to itunes inside the page of my app and inside the first tab "App Information" under the right hand side has a section "Others Information" click on the "edit user permission" and grant xcode user the permission to read the information of the app.

DONE

Upvotes: 1

Heestand XYZ

Reputation: 2231

Double check the Bundle OS Type code in your App's info.plist, for me, the only way around this error was to set it to APPL.

The weird thing is that the error was regarding to my frameworks bundle id, tho changing the above in my app solved it.

Upvotes: 6

Nasir Khan

Reputation: 881

In my case I was using a different account, I created an app on Itunes but selected different account on Xcode. So just Selected the right account on Xcode and it worked for me.

Upvotes: 1

Antoine Grenard

Reputation: 1892

In my case the problem was that my application had literally no information filled in the App Store Connect

Upvotes: 1

Baza207

Reputation: 2142

For me, what fixed it was to enter the required details in App Store Connect -> TestFlight -> Test Information.

Once I'd done that it seemed that Xcode realised there was a new app to allow uploading to and succeeded.

(Also check your caps in your Bundle ID though. 😉)

Upvotes: 2

Omar Al-Eisa

Reputation: 47

if your bundle id carried a capital letter and you've changed it to a lower case letter, you must run the application in the simulator before attempting to archive and upload to app store connect (this was the issue and solution for me).

Upvotes: 2

No suitable records were found verify your bundle identifier is correct

Answers (30)

Related Questions