[ios] Xcode Error: "The app ID cannot be registered to your development team."

We are porting an Android app to iOS for a client. They have added our account to their iTunes Connect account and created an app entry. We developed the app using the bundle ID they specified.

But now, when the app is ready for testing, we can't create a provisioning profile in Xcode. It is set to Automatic signing and this error is shown:

Failed to create provisioning profile.

The app ID "<bundle-id>" cannot be registered to your development team. Change your bundle identifier to a unique string to try again.

Our account is added as an App Manager in their iTunes Connect account, but still we can't take output with this ID. This error is not shown if we change the bundle ID in Xcode.

I had this same issue as OP and the problem was that I was invited only on appstoreconnect and not on developer.apple.com. After being invited as a member on developer.apple.com and going into the preferences in XCode, I got a new option to sign as a member of the organization. Setting signing team as member of organization in project settings fixed the issue. After that creating the provisioning profile was successful using automatic signage management.

You have to rename Organization Identifier on Bundle Identifier on settings tab.

Only by renaming the Organization Identifier error will remove.

If this persists even after clearing provisioning profile and re-downloading them, then it might be due to the bundle ID already registered in Apple's MDM push certificate.

Meet same Issue on one mac, but ok on another mac. I'm sure bundle ID is fine and unique.

I know it is provisioning profile issue, so Try refreshing the provisioning profile on your Local computer. Then It Works!

1. cd ~/Library/MobileDevice/Provisioning\ Profiles
2. rm *
3. Xcode > Preferences... > Accounts > click your Account and Team name > click Download Manual Profiles
4. Run app again

Changing Bundle Identifier worked for me.

1. Go to Signing & Capabilities tab
2. Change my Bundle Identifier. "MyApp" > "MyCompanyName.MyApp"
3. Enter and wait a seconds for generating Signing Certificate

If it still doesn't work, try again with these steps before:

1. Remove your Provisioning Profiles: cd /Users/my_username/Library/MobileDevice/Provisioning Profiles && rm * (in my case)
2. Clearn your project
3. ...

I encountered the same problem when I was trying to compile a sample project provided by Apple. In the end I figured out that apparently they pre-compiled the sample code before shipping them to developers, so the binary had their signature.

The way to solve it is simple, just delete all the built binaries and re-compile using your own bundle identifier and you should be fine.

Just go to the menu bar, click on [Product] -> [Clean Build Folder] to delete all compiled binaries

Clean Build Folder

None of the above answers worked for me, and as said in the original question I had also to keep the same bundle identifier since the app was already published in the store by the client.

The solution for me was to ask the client to change my access from App Manager to Admin, so that I had "Access to Certificates, Identifiers & Profiles.", you can check if it is the case in the App Store Connect => Users and Access => and then click on your profile (be sure to choose the right team if you belong to multiple).

Once you are admin go back to Xcode and in the signing tab select 'Automatically manage signing', then in Team dropdown you should be able to select the right team and the signature will work.

The bundle id (app ID) has a binding relationship with the apple id (apple id is the Apple development account, which also belongs to a certain development team). When the app is created, the bundle id (app ID) is already associated with you The development team is bound, so your app is being sent to other colleagues, he opens it in Xcode, and connects the real machine with a data cable to debug it will report the error as above;

To Solution

1. Follow the prompts to change the bundle id

   

2. Because some functions, such as third-party login, are bound to the bundle id to apply for the app key, etc., the bundle id cannot be modified. Then please find the apple id account registered by the bundle id before. Here, I will change It’s ok to become the apple id account I registered in the company group

3. If other colleagues in your group can run this app successfully on a real machine, it means that the "description file" corresponding to the apple id "certificate" used by him is correct.

Go to Build Settings tab, and then change the Product Bundle Identifier to another name. It works in mine.

This happened to me, even though I had already registered the Bundle Id with my account. It turns out that the capitalisation differed, so I had to change the bundle id in Xcode to lowercase, and it all worked. Hope that helps someone else :)

I delete the Bundle identifier in the https://developer.apple.com/account/resources/identifiers/list, then it works.

I had the issue with different development teams. I just checked the schema signings and picked the correct development team for the schemas that I needed:

I was able to get the original bundle identifier to work on my paid team membership account (after having it assigned to my personal team) by revoking the personal team signing certificate that was assigned to the same account id.

1. On the Apple Developer website sign in with the paid account it, go to Certificates, IDs & Profiles.
2. Click the personal team certificate.
3. Click the Revoke button.
4. Go back to XCode and try signing again. A new certificate will be generated that should work with the bundle id.

This won't work if you still need the certificate for other apps.

My problem was I was modifying the settings for the wrong version of my app.

I had "Debug" selected instead of "Release", so my bundle identifier was not accurate when it came time to Archive.