No matching records found. Verify that your package ID is correct.

Question

I created the application in iTunesConnect, and it was in a "ready to send" state for more than 3 days. When I try to archive my application and send it to the application store, it displays this message:

No matching records found. check your package id is correct

Answer 1

Now I find only an error. I used one uppercase letter in the package identifier. but I used small letters in the xcode package id. Now I have changed this, as in the application id. and now I have successfully downloaded my app to iTunes Connect. Thanks for your support.

Answer 2

Just make sure that the application that you configured on iTuneconnect has the same package identifier that you use to download the application.

Answer 3

as a rule, this happens when you did not create your application from the Apple developer account-> iTunes Connect-> click "My" App-> click the plus sign (+) → "Create" App-> and fill in all the information and Select a package identifier for the application you are downloading now.

Answer 4

If you use Application Loader, check if you are registered in the correct account. This was my case, and this can happen if you manage an account for different clients.

Answer 5

I believe that you can find the answer here Xcode 5 - "No application records found" when trying to check the archive from @Bamsworld.

As you mentioned and according to the documentation - Application Distribution Guide

Important: you cannot confirm your application if the recording of the application in iTunes Connect is not in a waiting state or later. After adding a new application in iTunes connect, an amber light will appear along with its status. Most likely, he will read "Preparing for Download." To get to the "Waiting for download" state, click the "Show details" button for the application, and in the upper right corner there should be a blue button "Ready to download the binary file". Click this button and follow the directions.

Answer 6

iTunes Connect || App Store Connect (website):

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

1. Add your new application / edit an existing application.
2. Go to application information.
3. Check the package identifier name.
4. If there is no package identifier, make sure you create one.
5. I used the package identifier WildCard. This means that your full package ID will most likely be com.organizationName. * And the suffix (exampleApp). Xcode:
6. Go to your workspace / project.
7. Go to your project.
8. Select the General tab.

Make sure the package ID is the name you provided in iTunes Connect.

For example: com.orgnanizationName.appName

It looks like you need to start the upload process in the App Store in iTunesConnect.

Answer 7

Using the Loader application worked in my case.

Answer 8

Verify your application ID at the Apple Developer Center. Then use the exact same name in the Bundler ID.

Answer 9

Double check the Bundle OS Type code in your info.plist application, for me the only way to get around this error was to install it in APPL .

The strange thing is that the error was related to my framework package identifier, but changing the above in my application solved it.

Answer 10

First, make sure that you use the same accounts for both the applications you download (or Xcode) and for connecting iTunes. Secondly, check that the packet identifier in the error message and in the iTunes connection match, including tEe cAsE !

Answer 11

if your package identifier contained an uppercase letter, and you changed it to a lowercase letter, you must run the application in the simulator before trying to archive and load the app connect into the application (for me this was a problem and a solution).

Answer 12

For me, what was fixed was to enter the necessary data in the App Store Connect → TestFlight → Test Information.

As soon as I did this, it seemed like Xcode realized that there was a new application that allowed it to load successfully.

(Also check your capitalization in your Bundle ID. 😉)

Answer 13

Check it once.

Open the .plist file and check the "Bundle OS Type code" key. If not, add a string, give this key and check the type, which should be a string. And give "APPL" as the value.

Clean the project and go to the Archive.

I hope this will work for you.

Answer 14

In my case, I processed it by opening the application loader inside Xcode.

Steps: Xcode → Open Developer Tool → Application Loader

When I opened it using Launchpad, it was not able to determine the correct account for the application. So he asked me to create an account.

With Xcode, the Application Loader can display a list of the accounts to which I am entitled. You must select the correct account from the drop-down list.

Answer 15

Be sure to follow these steps:

• Create an app id https://developer.apple.com/account/ios/identifier/bundle

• Build the app from iTunes Connect by selecting the Bundle ID you created in step one.

• Download IPA from Loader or Xcode

Answer 16

In my case, the application was already configured, but the version of the application was already used (while waiting for viewing), I just needed to increase the version number.

Answer 17

In my case, the problem was that in my application there was literally no information populated in the App Store Connect.

Answer 18

In my case, I used a different account, I created an application on iTunes, but chose a different account on Xcode. So I just chose the right Xcode account and it worked for me.

Answer 19

I have to manually sign the application. A new certificate and a new profile have been created. Set the code signature to Manual. Only then could I download. In addition, select the manual entry from the organizer when loading the assembly.

Answer 20

IMessage extension : for anyone struggling with this problem with the message extension (or any other extension), make sure that you enter the application’s goals, not the extension’s goal, in the "App Store Connect" → "General Information" → Bundle-ID. We fought 2 days to find out.

Answer 21

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

Answer 22

After hours of disappointment, I came across this article ....

Should the package identifier be case sensitive?

Hope this helps someone having the same issue as me.

Answer 23

In my case

• Checked if same user in itunes and xcode
• Verified packet identifier matches

Decision:

Go to itunes inside the page of my application, and inside the first tab "Application Information" under the right side there is a section "Other Information", click "Change User Permission" and give the xcode user permission to read information about the application. Appendix.

MADE

Answer 24

If after you confirm the match of the package identifier in the App Store Connect, Apple Developer Portal and Xcode and you still have problems, try this:

Remove the Apple ID associated with the Bundle ID you are having problems with from the list of accounts in Xcode (Menu Bar → Xcode → Settings → Accounts). Then add the Apple ID back to the list of accounts in Xcode.

Answer 25

Please check the uppercase and lowercase letter when assigning the package identifier.

It is also case sensitive. So make sure your package ID is identical.

Answer 26

What I managed to fix was to allow access to applications for all users:

1. Go to AppStore Connect
2. Go to my app
3. In the "More Information" section, click "Change user access."
4. Select "Full Control"
5. This allowed me to download the application for the first time (via Xcode and Application Loader)

After the initial download, I can go back to "Limited Access" and download just fine.

Answer 27

I changed the version number, but forgot to change the build version. Changing the build version solved the problem. Such a stupid mistake. Smh ...

Answer 28

Make sure this is included in your Info.plist:

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

I had an APPL with an error as an AAPL. As soon as I fixed it and entered Application Loader and Xcode with the same Apple ID, it worked.

Answer 29

For me, this was because I forgot to create a “Collateral Profile” on the Apple Developer Portal. I created a profile here for the "App Store", then downloaded and opened the file, and it worked!

Answer 30

Since this question obviously has different potential answers depending on individual circumstances, I decided to add my problem and what solved it:

Problem: I asked someone to copy the binary archive, make some changes, and then transfer the binary file to me. This caused a binary conflict.

Solution: I had to create a new certificate. I copied the package identifier from the development consul, pasted it into xcode and was able to download.

Note: You can restore the new package identifier by enabling "In-app purchases" in the Features section.