An App ID with Identifier '' is not available. Please enter a different string

IosXcodeApp StoreProvisioning ProfileApp Id

Ios Problem Overview


I am trying to add a new APP ID to prepare for App Store submission and got the following error under the bundle ID I provided.

> An App ID with Identifier 'com.domainName.AppName' is not available. Please enter a different string.

What does this mean? I am trying to add a brand new App ID, of course it does not exist.

What am I missing? I do not remember experience the problem last time I create an App ID.

Ios Solutions


Solution 1 - Ios

update

As of Xcode 8, iOS Team Provision Profile Managed by Xcode are now updated by Xcode automatically and correctly. They are not even listed at the Developer Portal, but generated on-the-flight.

However, the solution proposed below will still work. I've switched to using the automatic provisioning profiles.

tl;dr

Remove INVALID iOS Team Provision Profile Managed by Xcode from Developer Portal and manually create iOS Developer Provision Profile. Download it via Xcode and you should be good to go.

details

Problem:

I started to experience this after Xcode 7.3 (7D175).

What I did before the issue:

  • renewed Certificates (developer & distribution) via Xcode, b/c of their expiration;
  • installed two required certificates (developer & distribution) in my keychain;
  • re-generated Ad Hoc and App Store Provision profiles at Developer portal with new distribution certificate;
  • downloaded locally Ad Hoc and App Store Provision profiles via Xcode;
  • walk the project through the process of Setting up Xcode to automatically manage your provisioning profiles
  • noticed iOS Team Provision Profile Managed by Xcode was INVALID
  • saw Xcode being not able to Build & Run due to INVALID iOS Team Profile.

Tapping "Fix Issue" (the only way, I know to make provision profiles managed by Xcode valid), given the error An App ID with Identifier '<app id>' is not available.

Solution:

I have:

  • manually removed INVALID iOS Team Provision Profile Managed by Xcode from Developer Portal
  • manually created iOS Developer Provision profile
  • Downloaded it via Xcode

Now, I am able to Build & Run app to my devices.

Solution 2 - Ios

TL;DR Xcode is very particular about the name you give your App ID in the member center. Having the correct bundle identifier is not enough. You must use the specific format shown below for Xcode to "see" your App ID.

Update: According to @isaacselement in the comments below, this issue has been resolved in Xcode 7.3.1.


@romrom's solution of deleting the App ID and having Xcode create a new one was a clue. Unfortunately it was a nonstarter for me since my App ID was used by a Store app and therefore could not be deleted.

However, I discovered through some experimentation that I could solve the problem by manually editing the exiting App ID. It turns out that Xcode is really picky about the name of the ID, and not just the bundle ID.

For a typical bundle ID such as com.mycompany.appname, the App ID name must be in this format:

XC com mycompany appname

a name in any other format won't be seen by Xcode.


How to check if you're affected / How to Fix

  1. Log in to the [Member Center][1].
  2. Click on "Certificates, Identifiers & Profiles".
  3. One the left-hand navigation bar, click on "App IDs".
  4. Locate the App ID with your bundle identifier.
  5. If that App ID doesn't have the correct name format (as shown above), click on it then click the Edit button.
  6. Change the name and click Done.
  7. Enjoy the reduction in stress and anger.

P.S. There are some related problems if you're using Xcode 7.3 in which it won't automatically create proper distribution profiles for you, even if you fix the name as I mentioned above. The solution is to downgrade to 7.2.1 or 7.3 Beta or use a tool like fastlane/sigh.

[1]: https://developer.apple.com/membercenter/ "Member Center"

Solution 3 - Ios

I had the same issue and solved by following steps below:

  1. Go to Xcode Preferences > Accounts > Choose your Apple ID account

  2. Tap on View Details

  3. Tap on Download all and then Done

However it was working fine earlier but I don't know the reason why it stopped suddenly. I have gone through the steps above and found it working properly.

Solution 4 - Ios

You may have no app with that same ID, but someone else may. The IDs must be unique globally, and not only within your own apps.

Solution 5 - Ios

Solution for Xcode 7.3.

Go to

Member Center -> Certificates, Identifiers & Profiles -> Provisioning Profiles -> All

Member Center: https://developer.apple.com/membercenter

Find certificate for your App ID, it should be invalid, Edit, Select your iOS Distribution certificate, Generate. Go to:

Xcode -> Preferences -> Accounts -> View Details -> Download all

Invalid certificate

Generate step

Solution 6 - Ios

Version 7.3 (7D175)

The Application ID Name should be same as application bundle identifier, if you application bundle identifier is com.abc.xyz than the application ID name for this bundle ID should be XC com abc xyz

enter image description here

A name in any other format won't be seen by Xcode.

Solution 7 - Ios

I had this problem, too. It turns out that the problem and solution are quite simple. When an Xcode user runs an app on a device using their free personal account, the Bundle ID is registered to the personal account. Then, when the user upgrades to a paid Apple Dev account and tries to create an App ID using that Bundle ID - the backend system thinks that Bundle ID has been taken.

Fill out the form here at this website: https://developer.apple.com/contact/submit/ under the "Certificates, Identifiers, Profilescategory”. I did this and the problem was solved in less than 12 hours. This was Apple’s emailed response: "When you install an app on a device from Xcode using your Personal Team, the Bundle ID is registered to that account. I have deleted the Bundle ID "com.AppVolks.Random-Ruby” so it can now be registered on your paid membership.”

Hope that helps!

Solution 8 - Ios

TARGETS->General->Identity

At first, modify the value of 'Bundle Identifier', so that it is different from the previous value.Then team chose 'None'. Xcode6~Xcode7.3.1

enter image description here

Solution 9 - Ios

Same issue happened with me, it might be that Xcode automatically selected another team name, its solved by choosing my correct team name. Good luck !

Solution 10 - Ios

I got solution for this kind of problem by selecting this option at the time of build export.

enter image description here

Regularly I select second option for build export process but after installing Xcode 7.3 when I try to export build at that time I receive above error. After some sort of forum discussion, I conclude that I need to select last option now to export build.

I hope this information become helpful to other members of forum as well.

Solution 11 - Ios

If you've updated your profiles, and none of the other good answers are working for you, try selecting "Use local signing assets" when it asks you to "select a Development Team to use for provisioning:". I'd made sure everything else was in order, but it still wasn't working. Using local signing assets worked perfectly.

Edit: It looks like Xcode 7.3.1 fixes this issue. "- Fixed an issue that could prevent the export of an ad-hoc build from an archive"

Solution 12 - Ios

I received the same error after a reinstall of the OS on my developer mac and upgrading to xcode 7.3.

The Download all -button was my savior. enter image description here

Solution 13 - Ios

In my case, the problem was, that the identifier had too few dots.

com.example.foo wasn't accepted

com.example.foo.bar works

Solution 14 - Ios

I faced the same problem when i upgraded my Xcode to 7.3 and it showed me the same error in every project. The simplest solution that i found was to just the remove the apple account from Xcode and add it again. enter image description here

To remove just go to Xcode > Preferences > Select the account and click on - sign.

enter image description here and to add click on + sign and add the apple ID corresponding to your app.

After you add the account your problem would be solved.. If in case this still doesn't work . Then perform a next step of regenerating the profile (just click edit and then generate ) and then downloading your provisioning profile again and run it. I bet that would work .

Hope this helps. All the best

Solution 15 - Ios

I had the exact same issue. My problem stemmed from beginning app development under a free developer account and then switching app development to subscription (paid) developer account. The original free developer account already had registered the bundle identifier that your paid developer account is trying to use.

You can verify that this is the problem by going to Xcode -> Preferences -> Accounts -> and then look under Team. If you see both your free (personal) team and your new paid team both listed then your probably having the same issue I had. The two teams are interfering with each other and you need to remove the free (personal) team now that you want to use your paid developer account.

Unfortunately, the only solution is to call apple development support at 1-800-633-2152 (US & Canada) and have them deactivate the free (personal) account from the app so that your paid developer account can register the bundle identifier.

Solution 16 - Ios

I realize this couldn't have been the cause of the original problem, because Xcode 6 wasn't available then, but I'll leave the answer anyway in case it helps someone.

Xcode 6 now registers your bundle ID for you automatically, so you don't have to. It'll be somewhere in the list on a line starting with "Xcode iOS App ID".

Solution 17 - Ios

In my case it wasn't letting me because I set bundle id in xcode project BEFORE creating online, so I changed temporarily in xcode, created online then changed back to normal in xcode.

Solution 18 - Ios

When I experienced the "An app with identifier XXX is not available" error in trying to switch on iCloud support in Xcode's Capabilities tab, I found that I had to:

  • Give my app an explicit custom bundle id,

  • Register my app manually at the Member Center, explicitly requesting iCloud support entitlements there.

After that, switching on iCloud support in Xcode worked. So, I suggest trying the same thing. Sometimes, things work better when you do them at the Member Center.

Solution 19 - Ios

For me, the problem happened because I first created a new AppID and then created a new app with the bundle identifier of the AppID in iTunes Connect, and then tried to connect my development app with the AppID from within Xcode.

In this case, Xcode assumed that the AppID has already been registered by someone.

To resolve the issue, you first change the bundle identifier in your app (in iTunes Connect's MyApp section) to some temporary values (or if you don't have any, create a dummy AppID such as com.yourcompany.testapp), delete the AppID in Certificates, Identifiers & Profiles page, and try connecting it from within Xcode, not from within Certificates, Identifiers & Profiles, by pushing the fixing issue button in Xcode.

Solution 20 - Ios

Update to Xcode 7.3.1, they have fixed this bug.

Solution 21 - Ios

I just had this problem. This is my configuration:

I've got an iPhone Developer Certificate in a developer account (Apple Store) and an Enterprise account. These 2 certificates have the same name in my keychain: iPhone Developer : firstName lastName

I assume Xcode doesn't know which one to take and pick the wrong one.

I fix it by selecting the good one in Xcode > Build Settings > Code Signing. It was previously set to iOS Developer.

Solution 22 - Ios

I had same problem and the quick fix is:

  1. Remove bundle id from General tab of Xcode
  2. Go to info.plist file and put bundle id for the Bundle identifier field.

Clean and run. That's it.

Solution 23 - Ios

Purge or Fix all of the invalid and expired provisioning profiles. Even though they appeared to be unrelated.

We encountered this when we attempted to recompile an app that was previously working fine. Nothing worked until we cleaned up the provisioning profiles.

Then click on "Download All" under the "Provisioning Profiles" area of the Apple Id account for the appropriate team.

Possibly related to XCode 7.3

Solution 24 - Ios

enter image description here

I had the same issue on submission process and solved by Selecting Appstore provision instead of AdHoc. Simple!!

Hope this helps. All the best :)

Solution 25 - Ios

If you encountered this error while making an ad hoc deployment, this is now fixed in the XCode 7.3.1 release (May 3th, 2016) : https://itunes.apple.com/us/app/xcode/id497799835?ls=1&mt=12

> Changelog 7.3.1 : > > - Git updated to version 2.7.4 to improve security > - Fixed an issue where turning off a capability in the Xcode editor could leave the entitlement enabled in the app bundle > - Fixed an issue that could prevent the export of an ad-hoc build from an archive > - Fixed a crash when importing localizations

Solution 26 - Ios

This is for those who bump into the odd case I did, you CANNOT use the keyword test in the bundle id.

We were needing to test sharing data through the app group feature and the companion app wasn't developed yet so we simply changed the bundle identifier to test.APP_NAME instead of company.APP_NAME. We set up everything in iTunes Connect and nothing worked right. We then swapped the name to beta.APP_NAME and Xcode was able to manage the app id correctly again.

Normally to fix this issue, verify your provisioning profiles and App Id's have the correct settings, and if your still having trouble to to Xcode -> Preferences -> Accounts -> View Details -> Download All and you should be good.

Hope that helps.

Solution 27 - Ios

This may only apply to the latest version of Xcode (7.3 D175), recently release:

> Press the Try Again Button

After several hours of fiddling with Xcode build settings and starting the Certificate/App ID/Provisioning Profile dance from scratch, I ended up at the same place, same error message, App ID not available.

In frustration, I pressed the Try Again button thinking it was futile. But it worked.

Solution 28 - Ios

I had this same issue in Xcode 7.3. To solve it I performed the following:

  1. Deleted the provisioning profile on the developer portal website.

  2. Created a new development provisioning profile manually on the portal website.

  3. Added new profile in Xcode under Preferences -> Accounts -> Apple ID -> View Details. Attempting to just click the download button beside the new profile kept giving me an error. It was only when I clicked "download all" at the bottom that it finally downloaded and fixed everything.

Solution 29 - Ios

I had Distribution Provisioning for my Apple ID for the App Store only and still gave me that error: An App ID with Identifier '' is not available. Please enter a different string

I recently updated to Xcode 7.3 and probably that caused the issue. So what I did was creating iOS Development Provisioning by selecting all devices that I want to test in iOS Dev. Center (Member Center). Then Opened Xcode -> Preferences and under my account downloaded the newly created Development Provisioning for that App ID. When did that, the error disappeared.

Solution 30 - Ios

This seems to be a bit of a generic message. I'm sure many of the answers are correct. For me it was a mismatch between the entitlements and settings for the app in the member portal. My solution was this:

  1. Verify your bundle id matches the portal
  2. Verify your app in the portal has the same entitlements enabled as your project's entitlements file
  3. Verify your provisioning profile is valid and edit/regen if not
  4. In Xcode properties > Accounts double click on the account and tap the "download all" button
  5. Clean
  6. Try again

Solution 31 - Ios

If nothing else works, which was the case for me, try making a new app id that is longer, more unique, and possibly add some numbers.

Worked for me.

Solution 32 - Ios

com.domainName.AppName

this is the bundle identifier. based on this identifier only once can send push notifications and inapt purchases. so app made this as an unique id for app. So try with a new name as "com.domainName.YourName"

Solution 33 - Ios

I had a similar issue. I check all settings in Xcode all were proper. When I tried to upload app using Archive it was giving an error

"An App ID with Identifier 'com.myappname.yyy' is not available. Please enter a different string".

Then after I tried to upload app via "Application Loader" and got success!

Solution 34 - Ios

If not the AppId's business,just try to change the Team in TARGETS/identity to your company's team.

Solution 35 - Ios

I had generated the developer profile but not the distribution profile. I did that via the Apple Developer Member Center -> Certificates, Identifiers & Profiles -> Provisioning Profiles.

Next I downloaded these in Xcode via the Preferences->Accounts.

Solution 36 - Ios

With Xcode 7.3 I started seeing that issue.

Eugene Dubinin's solution did work, however it was causing issues with the same error if you're using App Groups.

It seems Xcode doesn't like at all you create the App IDs manually. I succeeded at fixing the issue by first deleting the manually created App ID on the developer portal. Then I let Xcode 'Fix the issue' by itself. The App ID got created successfully and the problem was solved.

Solution 37 - Ios

For me the solution was to change the bundle identifier by replacing the period separator to dashes. I changed com.mycompany.appname to com-mycompany-appname.

Solution 38 - Ios

I was having the same issue after the Xcode 7.3 update and nothing worked. The fix is really simple, please follow the answer here, it worked for me: https://stackoverflow.com/a/34346556

Solution 39 - Ios

I had the same problem since XCode 7.3. For my case, there was a _ in my AppId name and it didn't work even if the AppID was correct : com.mycompany.appname.

I had to edit the AppId in itunes member center to get this warning.

To resolve this bug, I renamed the AppId, generate a new certificate and new provisionning profiles.

Solution 40 - Ios

for me, i had to make sure an app with that bundle id was already created in the itunesconnect portal : /

Solution 41 - Ios

Nothing wrong with App Id in my case, but fix certificate and provisioning file first, then update to Xcode 7.3.1, clean, archive and submit, it works for me.

Solution 42 - Ios

For me, I was trying to create an app ID for an Enterprise app. The app ID had "xxx.ios.yyy" in it and it did not like the .ios. bit in the middle. As soon as I removed the ".ios" part I was able to successfully register it. This happened to me twice with two different app IDs of different length, and in each case, removing the ".ios" segment fixed the problem.

Solution 43 - Ios

I am using Xcode 12.4. And I have been facing this issue with Free account. Now I added Bundle Id to my paid account. Went through above answers but no luck.

Following steps solved my issue. You may try once. thanks

Actual scenario so far I realized :

  1. Main thing is when you build with Xcode then Bundle Id auto registered with account[free account]
  2. Same Bundle Id is not working for new Paid account bcz of duplicacy
  3. For free account it is not possible to remove app/Bundle Id from App Store Connect
  4. So have to change Bundle Id for new Paid account.
  5. If it was paid account then possible to remove Bundle Id from App Store Connect

Steps :

  1. Sign with free account again on Xcode Team
  2. Sync with Xcode which create provisioning profile to sync
  3. Then change Bundle Id to com.domain.appnamefree and sync with free account again
  4. That means apple auto registered with this Bundle Id for this free account
  5. Once this change got applied, the real bundle id became free and available
  6. Then delete the free account from Xcode account
  7. Now add paid account to Xcode Team
  8. Change Bundle Id to com.domain.appname
  9. And sync again so that apple recognised this Bundle Id for this Paid account

enter image description here

enter image description here

Solution 44 - Ios

I had the same problem, when I use Xcode7.3 it. I solved the problem: I created a new profile select Ad Hoc, and then downloaded to Xcode.That‘s OK!

enter image description here

Solution 45 - Ios

Me also got the same issue.

In my case i already registerd with my free account. We can't delete that app bundle id from our free account.

So i changed bundle id not app name and again i tried it's working.

Solution 46 - Ios

None of the above answers helped me, but I just found the solution.

For those who couldn't benefit from any of the above answers;

I have 2 different teams as you see.

I noticed that I did debug before with other team and Xcode automatically created an App ID in second team's developer account.

I opened https://developer.apple.com/ for second team's account and removed auto-created APP ID

Then worked fine

enter image description here

Solution 47 - Ios

Downgrade to xcode 7.2.1 - it worked for me.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
Questionuser2265763View Question on Stackoverflow
Solution 1 - IosYevhen DubininView Answer on Stackoverflow
Solution 2 - IosOz SolomonView Answer on Stackoverflow
Solution 3 - IosAmit AjmeraView Answer on Stackoverflow
Solution 4 - IosGuilhermeView Answer on Stackoverflow
Solution 5 - IosVladislavView Answer on Stackoverflow
Solution 6 - IosImranView Answer on Stackoverflow
Solution 7 - IosLevi LaisView Answer on Stackoverflow
Solution 8 - IosylgwhyhView Answer on Stackoverflow
Solution 9 - IosAaoIiView Answer on Stackoverflow
Solution 10 - IosSiddharthView Answer on Stackoverflow
Solution 11 - IosSmeedgeView Answer on Stackoverflow
Solution 12 - IostommysView Answer on Stackoverflow
Solution 13 - IoslilalinuxView Answer on Stackoverflow
Solution 14 - IosKunal GuptaView Answer on Stackoverflow
Solution 15 - IosAlecView Answer on Stackoverflow
Solution 16 - IosDan WesnorView Answer on Stackoverflow
Solution 17 - IostemirbekView Answer on Stackoverflow
Solution 18 - IosmattView Answer on Stackoverflow
Solution 19 - IosBlaszardView Answer on Stackoverflow
Solution 20 - IosMannView Answer on Stackoverflow
Solution 21 - IosRémyView Answer on Stackoverflow
Solution 22 - IosVinod MahaleView Answer on Stackoverflow
Solution 23 - IosAnthonyVOView Answer on Stackoverflow
Solution 24 - IosVinu David JoseView Answer on Stackoverflow
Solution 25 - IosJonathan F.View Answer on Stackoverflow
Solution 26 - IosUnomeView Answer on Stackoverflow
Solution 27 - IosAnthony CView Answer on Stackoverflow
Solution 28 - IosRobert WasmannView Answer on Stackoverflow
Solution 29 - IositzoView Answer on Stackoverflow
Solution 30 - IosAnthonyView Answer on Stackoverflow
Solution 31 - IosKhouryView Answer on Stackoverflow
Solution 32 - IosCharan GiriView Answer on Stackoverflow
Solution 33 - Ioskb920View Answer on Stackoverflow
Solution 34 - Iosxiaofei xuView Answer on Stackoverflow
Solution 35 - IosSteve TauberView Answer on Stackoverflow
Solution 36 - IosromromView Answer on Stackoverflow
Solution 37 - IosSteve BardenView Answer on Stackoverflow
Solution 38 - IosMohit SinghView Answer on Stackoverflow
Solution 39 - IosvmeyerView Answer on Stackoverflow
Solution 40 - IosgreenhouseView Answer on Stackoverflow
Solution 41 - IosYao LiView Answer on Stackoverflow
Solution 42 - IoschadbagView Answer on Stackoverflow
Solution 43 - IosMimu Saha TishanView Answer on Stackoverflow
Solution 44 - Ioswu qiuhaoView Answer on Stackoverflow
Solution 45 - IosNareshView Answer on Stackoverflow
Solution 46 - IosUchiha SasukeView Answer on Stackoverflow
Solution 47 - IoshaithngnView Answer on Stackoverflow