Xcode Error: “The app ID cannot be registered to your development team.”

Question

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

Answer 1

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

Answer 2

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.

Answer 3

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

Answer 4

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

Answer 5

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.

Answer 6

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