I have an existing app with bundle identifier com.brs.paysrc example and the app is live on store. It was created using a wildcard app id. Now i want to enable push notifications for this app. So i tried to create a new app id with b uncle identifier as com.brs.paysrc but it give some an error saying There were errors in the data supplied. Please correct and re-submit. An App ID with Identifier 'com.brs.paysrc' (example) is not available. Please enter a different string.
(I'm not sure if this'll help you...)
I had the same issue with an app our company has in the App Store.
The reason was because we have both a Developer Program (so we're allowed to submit an App onto the App Store) and an Enterprise Program (so I can make in-house copies of the app).
Our Bundle ID was registered under the Developer Program, but I had logged into the Apple Developer website and had chosen the Enterprise Program group.
In the Apple Developers website, the Identifies\App IDs didn't show our Bundle ID, because it was actually registered under our Developer Program... but, of course, it still refused to let me create the Bundle ID a second time, and, as usual, the error message gave no clue as to what the problem was.
I really hate the whole Certificates/Provisioning Profile stuff with Apple. Their error handling/reporting, when you get something wrong, is a farce. And it'll happily let you create non-working apps, deploy them to a device, then report a "Your app could not be installed at this time" when things go wrong.
Even yesterday, when I was ready to deploy a new version of the App to the App Store, I could create an Archive, the Validate said it was all fine, but then when I submitted it, it reported 3 errors in my .plist file.
Oh, and remember that your Bundle ID is stored in the .plist file and in the settings:
Make sure this Bundle ID is correct in both places!
(Sigh.)
You might have clicked it twice (I did). Check here, to see if your id is there: https://developer.apple.com/account/ios/identifier/bundle
Please give unique bundle ID, it will resolve your problem. Sometimes the same bundle ID is already used by another app. Hence this issue occurs. Try with different bundle ID it will resolve your problem.
I'm having a problem whereas I cannot submit my archive for beta testing due to this problem (keep in mind I've already got a build out for testing, uploaded a while ago):
Xcode attempted to locate or generate matching signing assets and failed to do so because of the following issues.
An App ID with identifier '' is not available. Please enter a different string
According to this question, it seems that I should change my bundle ID from the format I am currently using: com.my.app, to the preferred format: com.my.app.XXX.
However, how can this be achieved? I'm using Firebase version 3 from Google as my backend provider, and I cannot seem to change the Bundle ID there, even if I would take the big step to create a whole new app in iTunes Connect due to not being able to changing the bundle ID.
My limitations (it seems):
Can't change bundle ID at Firebase
Can't change bundle ID with project in iTunes Connect.
Can't delete app identifier in member center because it's being used by the app listing in iTunes Connect.
Can't delete app from iTunes Connect.
Hence I'm a little stuck here; what's the best way to dig out of this?
I found that my app's bundleIdentifier is different from my App ID of iTunes. So I want to make new appID, but I can not make App ID having bundleIdentifier 'com.A.B' different from the one of App ID that I already have one :'com.A.C'. So I try to remove one I have but when I tried, it says
An unspecified error occurred.
The App ID 'ABC1D2FG3.com.A.C' appears to be in use by the App Store, so it can not be removed at this time.
So I removed all certificates and provisioning profile belonged to that AppID. But it still says same message.
I think the image is the problem. I set to upload my app, but I don't know how to cancel it.
You need to remove your app from the App Store first.
According to this document, you can only delete your app if it has at least one approved version and is currently in one of the following statuses:
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.
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.
generally this happens when you have not created your app from apple developer account->iTunes Connect->Click on My App->click on plus sign (+)->New App->And fill up the whole info and Choose Your Bundle Id for the app you are uploading now.
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
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.
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.
I believe you can found the answer here Xcode 5 - "No application records were found" when trying to Validate an Archive from #Bamsworld.
As you already mentioned and as per the documentation - App Distribution Guide
Important: You can’t validate your app unless the app record in iTunes Connect is in the “Waiting for Upload” or later state
After you add a new app in iTunes connect there will be an amber light along with its status. It will most likely read "Prepare For Upload". To get it to the "Waiting For Upload" state click view details for the app and in the top right there should be a blue button that says "Ready to Upload Binary". Click this and follow the given directions.
If you use Application Loader, then check if you are logged to the correct account. It was my case and it can happen if you manage account for various clients.
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.
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.
Using Application Loader worked in my case.
Chek your app ID in the Apple Developer Center. Then, use exactly the same name in Bundler Identifier.
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.
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.
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...
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.
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.
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.
Firstly, check that you're using the same accounts in both Application Loaded (or XCode) and iTunes connect. Secondly, check that Bundle Id in error message and in iTunes connect are match, including tHe cAsE!
Make sure you follow these steps in order:
Generate the App ID at https://developer.apple.com/account/ios/identifier/bundle
Generate your app from iTunes Connect selecting the Bundle ID created in step one
Upload the IPA from Application Loader or XCode
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).
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. 😉)
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.
For me : Just tried uploading using Application Loader and it worked
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.
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!
In my case I got it worked with opening the Application Loader inside the XCode.
Steps : XCode -> Open Developer tool -> Application Loader
When I opened it with Launchpad it failed to identify the correct account for the app. Therefore, it asked me to create an account.
With XCode , Application Loader could list down the accounts I'm entitled for. You have to select the correct account from the drop down.
In my case the app was already set up, but the app version was already in use (waiting for review), I just needed to increase the version number.
In my case the problem was that my application had literally no information filled in the App Store Connect
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.
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
I just got this warning when submit my app to app store, it is just warning, not error. This app was transferred from another developer account to my account before, so the prefix of the App ID is changed.. I think this should be unavoidable, but since I got this warning, what does it affect my app actually? What Keychain access would be lost?
Have you transferred the app from another developer account to your one? The previous provisioning ID will obviously be different.
UPDATE - For clarification
I have noticed that this answer is getting a lot of views so I will just edit it to include my further explanation from the comments below.
Basically the previous version of your application will NO longer be able to access keychain in order to save secure strings such as passwords (if it contains this functionality). This is because the distribution/provisioning profile it was signed with contains a different ID than the one you are using in your new distribution/provisioning profile because you have transferred your app from a previous account to your new one.
However any NEW versions of your app which are signed with the latest distribution/provisioning profile WILL be able to access keychain as normal in order to save secure data if they need this functionality because they are signed with a distribution/provisioning profile which contains the latest App ID for that app.
The warning informs you that your updated app will not be able to access items previously saved in the keychain. The old version of your app can still access and store items in the keychain, just like the new version. However the two versions cannot share information in the keychain.
In summary, all data saved in the keychain will be lost once a user updates to the new version. All information stored in UIPasteboard will also be lost.
You can see this message if:
The app was transferred to your account and you are updating it for the first time. In this case there is nothing you can do to prevent the warning (and side effects).
Your app was added to iTunes Connect before June 2011 and you recently updated the provisioning profile used by the app. Either your old provisioning profile was using a wildcard (*) App ID and the new one is now using a specific App ID, or the opposite (less likely). In the later case you can switch back and avoid the warning (choose the correct provisioning profile in Xcode). In the other case, chances are your app needs access to services like Game Center, Push Notifications (or anything that a wildcard App ID will not let you use) and you cannot avoid the warning.
If you want more details, the warning is related to the fact that App ID prefixes are attributed by Apple and cannot be changed. Check the "App IDs" section in Apple's "Certificate, Identifiers & Profiles" page (https://developer.apple.com/account/ios/identifiers/bundle/bundleList.action - you need to sign in), press on an ID and look at the "Prefix" field. You can also check Apple's Technical Note 2311 https://developer.apple.com/library/ios/technotes/tn2311/_index.html
Lastly, you might thing you could avoid the warning by changing the Keychain Access Groups (keychain-access-groups) field of your provisioning profile. This will not work as Apple will not let you have different prefixes for the App ID and for the Keychain Access Groups.
As of the stricter security in iOS 8.1.3, this is much more serious than the warning suggests; see https://developer.apple.com/library/ios/technotes/tn2319/_index.html#//apple_ref/doc/uid/DTS40013778-CH1-ERRORMESSAGES-UPGRADE_S_APPLICATION_IDENTIFIER_DOES_NOT_MATCH_THE_INSTALLED_APP. It seems like the mismatch causes a failure to upgrade to the new version. When I try to update via Xcode, it fails with an error to the device console like that in the Tech Note: “Upgrade's application-identifier entitlement string [....] does not match installed application's application-identifier string [....]; rejecting upgrade.” Trying to update via iTunes seems to fail silently.
I hope that the answer is simply “this error is simply an indication that Xcode has chosen the wrong provisioning profile,” verified as in https://developer.apple.com/library/ios/technotes/tn2318/_index.html#//apple_ref/doc/uid/DTS40013777-CH1-TNTAG65. But I last submitted my app many Xcode versions ago, and finding the right one may be a challenge.
Note the phrasing “Xcode has chosen the wrong provisioning profile”; to make sure that it chose the profile you thought you chose, click on the arrow next to the chosen profile’s truncated name in the archive verification dialog. To double-check this, submit to the App Store with a known error (I inadvertently used a missing icon), so that you see whether the warning appears.