An App ID with Identifier 'xxx.yyy.zzz' is not available. Please enter a different string when submitting new build - ios

Here I already added a new version of my app on the iTunesConnect, and the status of the new version is at 'Prepare for Submission'. However, I have a problem with verifying my new build and submitting it to iTunesConnect.
The Error I got is An App ID with Identifier 'xxx.yyy.zzz' is not available. Please enter a different string
Here I left out the Bundle Identifier because I do not want to expose my app ID anyway, but I certainly sure that the bundle Identifier, Version, and Build version is exactly the same as what I added to the iTunesConnect (1.20).
I also already archived the app, but got stuck at the verifying process, and got this An App ID with Identifier 'xxx.yyy.zzz' is not available. Please enter a different string error.
Is this the proper way to submit a new build to the iTunesConnect? I think the system should match the App Bundle ID with the one registered at the iTunesConnect's database, and simply verify and upload a new build for me. I do not really know what is wrong here. It seems that the XCode is trying submit the new app, but cannot go through because the Bundle ID is already registered (with the previous version).

You should check the certificate and the AppId

Let XCode automatically manage the certificates and profiles to use:
on the Project Navigator click on the app
go to Build Settings
find the Code Signing section
change the Provisioning Profile to Automatic from the drop-down
change the Code Signing Identity to iOS Distribution
if the project builds without errors, you can Archive, Validate and Upload to App Store
the build will be available on iTunesConnect
If something is missing XCode will ask to fix it for you.
This is not related to the app version on iTunesConnect.
When submitting a version for review you can chose the build to use.

I also encountered the same problem. Xcode7.2.1.
Effective solution is:

You can try:
Closing Xcode.
Opening the keychain,deleting the certificate with the corresponding key string.
Opening Xcode, Preferences -> View Details -> Reset Certificate
Choosing the right certificate.

Related

Failed to register bundle identifier

I need to put the latest version of the app on AppStoreConnect to test it on TestFlight.
I encounter a problem when archiving the project in order to upload it on AppStoreConnect and be able to add a new version of the app and test it on TestFlight.
I have been added as a developer in AppStoreConnect in the project.
So I added my profile in Xcode with the right email address. During archiving, these two errors appear:
Failed to register bundle identifier: The app identifier "com.xxxxx.app" cannot be registered to your development team because it is not available. Change your bundle identifier to a unique string to try again.`
No profiles for 'com.xxxxx.app' were found: Xcode couldn't find any iOS App Development provisioning profiles matching 'com.xxxxx.app'.`
I confirmed with the project manager the bundleID which is good: "com.xxxxx.app".
Despite several tries and research, I haven't found the solution to this problem, so I can't archive the app so I can add AppStoreConnect.
Thanks for your help
Trying changing Team to just "Your Name" without (personal team) extension. This is what worked for me.
Hey :) when opening preferences for Xcode do you see your company user account?
also when opening the target app underder singing & capabilities, do you see that it is all clear there or is there an error? (you should see that under signing certificate field your account is configured)
I think the solution is to change the XXXX in "com.xxxxx.app" to unique value like your name and last name for example : "com.zizou.app".

Validating error after archive in iOS

I am trying to upload this ionic project for iOS devices using Xcode 7.3. I successfully created all the certificates and app ids and then archived. But after that, when I click on the validate option I get an error, which I do not understand!
The error says:
Failed to locate or generate matching signing assets:
Xcode attempted to locate or generate matching signing assets and failed to do so because of the following issues.
An App ID with identifier 'com.*****.******' is not available. Please enter a different string.
THankx in advance
I got the same issue with upload from Xcode7.3. Before xcode7.3 that we dont need to create an app on iTunesConnect and we can create an IPA file and all the things. But i did Fix this issue by following:
Open iTunesConnect and login with Apple-id password.
Create new iOS app and select the identifier that we used in our Xcode project.
After that you just need go in Xcode and select device and create an archive.
Do the same step that you did before and the error goes away.
I got the same issue. Check the following steps :
1) Check if the bundle ID of your project in Xcode is same as the bundle ID associated with your AppID in Member Center.
2) Make sure you are selecting the correct Distribution Certificate and provisioning profile.
3) Make sure you have created an app on iTunes connect. Crosscheck the bundle ID there as well.
Now try to archive and validate again. Hope this solves your problem.

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.
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

iOS app submission : invalid signature

I'm struggling with this issue for more than a week now, I've tried all I could find on Google with no luck. This is my first time trying to submit an app to the App Store, but I keep getting this email after each try:
invalid Signature - Make sure you have signed your application with a
distribution certificate, not an ad hoc certificate or a development
certificate. Verify that the code signing settings in Xcode are
correct at the target level (which override any values at the project
level). Additionally, make sure the bundle you are uploading was built
using a Release target in Xcode, not a Simulator target. If you are
certain your code signing settings are correct, choose "Clean All" in
Xcode, delete the "build" directory in the Finder, and rebuild your
release target.
so here is what I'm doing:
I have my distribution certificate in login keychain , with the
private and public key .
I have the distribution provisioning profile with the same certificate i've created earlier .
The bundle ID on my provisioning profile is the same on my iTunes connect app and the
same in Xcode general settings .
The same version (0.8.2) in iTunes connect app and Xcode .
I'm building with device selected not a simulator (but i don't have a device connected to the mac).
the code signing part under build settings (for both target and project).
I have "iPhone Distribution : ... " for everything and also i'm selecting the distribution provisioning profile .
What I am missing? I've looked all over and all I find is people with incorrect versions or incorrect bundle id.
I am using Cordova and Ionic to build my app, I don't know if that has something to do with it.
I've seen the troubleshoot guide of Apple on this issue and ran this command:
codesign --verify -vvvv -R='anchor apple generic and certificate
1[field.1.2.840.113635.100.6.2.1] exists and (certificate
leaf[field.1.2.840.113635.100.6.1.2] exists or certificate
leaf[field.1.2.840.113635.100.6.1.4] exists)' /path/to/the.app
I get : a sealed resource is missing or invalid file modified: /path/to/MyApp.app/MyApp
they suggest to run this to resolve the issue: dot_clean path/to/xcodeproject
But that didn't help, I keep getting the same error.
Please help, I'm out of clues
EDIT ( Solution )
Apple is just a big stupid company, none of the suggested solutions under any of the posts helped me ! it was just the stupid process of apple , I had an invalid character "?" that should have been removed from the App Name. I wish Xcode coulde validate the name first before going into any of the submitting and testing process.
I think you are not using the proper distribution profile.Create a new distribution profile in itunes connect for app store submission not the ad hoc one. see the below image.
1)Then, check your bundle identifier that should exactly match with the newly created appstore certificate.
2)Just Delete your certificates in Provisioning Portal and update the new certificate in Xcode.
3)Goto Organizer / Provisioning Profiles / Refresh and allow Xcode to fetch the latest ones.
4)then go to project target->build settings->build options->validate product and change your release mode to yes. see the image below.
then,clean your project and generate the archive.
I had the same issue because the application archive contained files with non-ASCII characters. I renamed all of them and then it worked.
You can find all files with non-ASCII characters by executing the following command in the terminal from the archive folder path:
LC_ALL=C find . -name '*[! -~]*'
Build Settings-> Build Options: Enable Bitcode = Yes helped for me. I could see the error still, but waiting a little Xcode passed it, and continued to upload the application.
I had the same issue a couple of days ago and in the end I had to clean my distribution certificates from Keychain Access, remove and regenerate them from the developer portal. After reinstalling the certificates I was able to build and run the app on the physical device, then archiving it and sending over to the App Store.
All the steps you listed here are fine. If you can connect to a physical device and make sure your certificate is listed between brackets for the code signing settings.
I had to go through the same
frustration in order to learn that the best resource to learn how
Provisioning works is the App Distribution Guide.
Additionally, there are quite few threads on StackOverflow dealing with the same or similar issues like this one: App Submission: Invalid Binary - Invalid Signature
Good luck!
Make sure your bundle id should match with App ID and Change project edit scheme to release .
If not try this link http://stackoverflow.com/questions/5196309/ios-code-signing-fails-a-sealed-resource-is-missing-or-invalid
I have a same problem with xCode 13+, in my case i just replace the target name with not special caracter.
That fix solved my problem 99% because i have multiple targets on my project and some targets presented this problem because contained special carcters in the target name.
I did run into the same problem as this today, turned out to be a .DS_Store file in the Resource directory. Removed that file before building and then everything worked out.
I have a same problem. Then, I found the best solution to fix it.
Replace your Product Name of your App by the new name in which without Unicode Characters.
Go to [App] > Target [App] > Build Settings > Packaging > Product Name.
Fix Invalid Signature

contains entitlement values that are not supported

Have created an app-id as normal.
Then created an app-store distribution profile...as normal.
Set up the game in itunes connect
Installed the profile
Built the game with GS...all goes fine.
But when I upload my binary is rejected with that error : Invalid Code Signing Entitlements
Invalid Code Signing Entitlements :
The signature for your app bundle contains entitlement values that are not supported. For the com.apple.developer.ubiquity-container-identifiers entitlement, the first value in the array must consist of the prefix provided by Apple in the provisioning profile followed by a bundle identifier suffix.
The bundle identifier must match the bundle identifier for one of your apps or another app that you are permitted to use as the iCloud container identifier.
Specifically, value "(my team bundle seed id is here).*" for key "com.apple.developer.ubiquity-container-identifiers" in basejumpxl is not supported.
Really not sure what I have done wrong...as I have done this loads of times, and never had this issue
Anyone point me in the direction of what my obvious mistake might be??
I finally successfully submitted the app, and it's now "Waiting for Review" status.
The problem is with the new "Enable for iCloud" configuration in App ID's.
Here's what I did to fix it. Hopefully this will help anyone who's having this issue.
In iOS dev portal:
Save yourself some time and just go ahead and delete the provisioning file you previously made for the new app you're trying to submit. (you may have luck by simply renewing it, but probably not.)
Go to your App ID, and click on configure. Once in configure, UNCHECK "Enable for iCloud" and click "DONE". iCloud configuration is what's causing the error. (This option had disappeared earlier, but is back again.)
Make a brand new provisioning file for Appstore distribution, and select the proper app id.
Download this new provisioning file.
Add this newly downloaded provisioning file into Xcode's organizer. Easiest way is to just drag and drop the file overtop Xcode's app icon.
Re-publish your game in Gamesalad, making sure to choose the NEW provisioning file you just created. (I went ahead and deleted the problematic provisioning file so I didn't get confused and accidentally choose the wrong one when publishing.)
Re-submit through Application Loader.
Hope this helps. :)

Resources