An App ID with Identifier 'com.example.app.extention' is not available. Please enter a different string

Question

I have tried to add extensions to my iOS app, both a today extension and an Apple Watch app. My app has been completed however when submitting my archive I got the error based on my bundle identifiers. I then removed the extensions, added them back, and attempted to resubmit. However, xcode now complained that my provisioning profiles cannot be signed.

"An App ID with Identifier 'com.example.app.extention' is not available. Please enter a different string."

I immediately went to the member center to see if an App ID already exists that prevents me from using it for my extensions. Nothing conflicted with the name, this is what was so bizarre to me. Shouldn't I be able to make the new ID if it doesn't conflict with an old ID? I also removed any provisioning profiles from previous extensions. Still, I could not add either "com.example.app.extention" or "com.example.app.watchkitextension."

I decided to just create new app IDs, following a new naming convention like "com.example.app.extentions.watchkitextension." or "com.example.app.extentions.todayextention." Everything worked fine, and built fine. I installed on my devices, things were good. My archive even was validated. However, upon submission I am given the error:

ERROR ITMS-90347: "Bad bundle identifier. The bundle identifier "xxx.yyy.zzz" of the application extension xxx.app/Plugins/xxxExtension.appex should start with the application's bundle identifier "xxx" and not contain more than one period "." after the application bundle ID.

This means I have to use the naming convention "com.example.app.extention" that xcode and the member center will not allow me to create the proper IDs.

I am extremely frustrated, can someone please help. I cannot find a solution anywhere.

EDIT

It seemed that I was actually not able to use that identifier at all.

Also, I should note a couple of warnings for anyone with this message:

1) You cannot add anything before the extension of it includes a period, as in com.domain.app.extensions.extension won't work either. 2) The automatics Swift 2 converter has a tendancy to change identifieres to more standard names and try to let xcode work out the provisioning profiles. Be careful of this!

The only fix I had was to change the identifier name for good. I personally used com.domain.app.todayextension. I got it to work then, but only after installing and adding the correct provisioning profiles for development and distribution through the member center. It appears to be a bug in Apple's system, or maybe we all have absolutely no idea how provisioning profiles work. I think the latter is probably what is true. Anyway, I hope that helps!

Solution 1

I found the solution from Apple developer forums.

Apple has just updated their Dev Center CGU. It seems that the app extension bundleId is stricter.

if your app bundleId format is : com.my.app

your app extension bundleId now have to be : com.my.app.XXX

Creating new appID and provisioning profile fix the issue.

Check this link https://forums.developer.apple.com/thread/15712

Solution 2

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

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

If your application is already on app store and you are submitting update than just change the app ID name accourding to above formate and it will work

Solution 3

Xcode to 7.3

I have encountered this issue when archiving and in my case, downloading all provisioning profiles on preferences cant fix this so I update it.

Try to check your app's Provisioning Profile on Member Center.

Go to Developer > Certificate, IDs & Profiles > Provisioning Profiles > All

Look for your app's Development and Distribution Profile, check if status is Invalid then Edit,

Modify your profile contents and select the Generate button to save changes

Finally, Go to Xcode> Preferences > [Apple account] > View Details and Download All to refresh your provisioning profiles

Clean. Build. Archive. Success ! Hope it helps :)

Solution 4

Here is what worked for me on Xcode 7.3:

Check Devices in the Apple Developer member centre. Once a year you have the opportunity to reset the devices. After reseting devices you will notices your Xcode managed provisioning profile is invalid. To update this I went into Xcode > Accounts -> my Apple ID -> View Details and downloaded all provisioning profiles. I then built to device and then downloaded the provisioning profiles again for good measure

Solution 5

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

View more solutions

Comments

[crosscode]

Perfect. Selecting Team - "None" fixed it for me. I was able to rebuild, archive and submit it without any problem.

[MatterGoal]

What!? are you sure about that?!

[Keith Murray]

Um, holy cow, this actually worked for me too. Makes no sense to me.

[Imran]

@MatterGoal yes I am sure about it, although make no sense.

[XcodeNOOB]

But will that effect application which is already live or will it upload a new application to store with same name?

[Imran]

@XcodeNOOB for already live app you just have to rename your app ID

[theLastNightTrain]

Incredibly, this solved this ongoing persistently-returning problem for me too - great find @MuhammadImran

[David Jirman]

this should be marked as the correct answer (more info at stackoverflow.com/a/36343710/2609269)

[Andres C]

Somewhat late to the party... But this DID fix the issue for me :D

[Adam Davis]

Worked well for me. Thank you.

[ylgwhyh]

Sorry，I don't know for Xcode7.3. I have not updated.

[Keller]

According to the other SO thread, this is an Xcode bug that is fixed in 7.3.1.

[Mike Gledhill]

You idiots. (I'm talking to Apple, rather than you !) Fine, if Apple are going to make changes like that, fine... but at least display a useful error message explaining the change, rather than some misleading rubbish about it being "unavailable". God, I hate this Xcode stuff. They must really hate developers.

[Mohammad Alqurm]

Wow! This solution worked for me! Can anyone clarify why this happen ?

[Imran]

Its a bug in XCode 7.3 and is fixed in xCode 7.3.1

[Zoltan Vinkler]

Only this worked for me today with the latest Xcode version.

[Sheereen S]

great, exact solution

[rtcarlson]

Just when you think iOS development couldn't get any weirder.