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 "
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.
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!
cd ~/Library/MobileDevice/Provisioning\ Profiles rm * Xcode > Preferences... > Accounts > click your Account and Team name > click Download Manual Profiles Run app again
Go to Build Settings tab, and then change the Product Bundle Identifier to another name. It works in mine.
You have to rename Organization Identifier on Bundle Identifier on settings tab.
https://i.stack.imgur.com/bVGx5.png
Only by renaming the Organization Identifier error will remove.
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.
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 :)
Changing Bundle Identifier worked for me.
Go to Signing & Capabilities tab Change my Bundle Identifier. "MyApp" > "MyCompanyName.MyApp" Enter and wait a seconds for generating Signing Certificate
If it still doesn't work, try again with these steps before:
Remove your Provisioning Profiles: cd /Users/my_username/Library/MobileDevice/Provisioning Profiles && rm * (in my case) Clearn your project ...
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.
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.
My problem was I was modifying the settings for the wrong version of my app.
https://i.stack.imgur.com/7s8XK.png
I had "Debug" selected instead of "Release", so my bundle identifier was not accurate when it came time to Archive.
error message
The app identifier "my.bundle.id" cannot be registered to your development team because it is not available. Change your bundle identifier to a unique string to try again.
try this
Apple developer > Account > Certificates, Identifiers & Profiles > Identifiers
https://i.stack.imgur.com/rvnEw.png
https://i.stack.imgur.com/cQCm3.png
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
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:
https://i.stack.imgur.com/TN8wC.png
I delete the Bundle identifier in the https://developer.apple.com/account/resources/identifiers/list, then it works.
IF you are working with different build configs then check in Signing & Capabilities Tab are you using Correct Bundle Identifier.
https://i.stack.imgur.com/uWRFV.png
For Xcode v12 and above
Open the .xcworkspace file using Xcode
Then go directly to the General section, you'll see Bundler Identifier
Then change the name in the bundler identifier
for example com.myapp-dev.app
should be changed to com.myapp.app
.
This worked for me.
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.
On the Apple Developer website sign in with the paid account it, go to Certificates, IDs & Profiles. Click the personal team certificate. Click the Revoke button. 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.
If none of the above solutions work, you may want to check your folder names. I had another folder, within a separate parent folder but sharing an ancestor directory, with the same name as my project folder. Renaming the other folder to something else resolved the issue. If I had to guess, Xcode was looking for the project in the parent directory, found the alternate folder with the same name and got confused...
Due to Security issue my client do not want to share the personal credentials. He just add my apple id in developer.apple.com After that I create the certificate from key chain and add it into apple developer Account. My client also add the bundle identifier and send it to me the latest certificate Now you need to add Team account Note: You must add team account not your apple id account In my case i got 2 ids one of mine muhammadusman17....@gmail.com and the other one is "CHT Team" i just select the CHT Team then its working perfectly
At the center top of your XCODE screen, change your device.
For example: Apple Pie>iPad Pro (12.9-inch)(5th generation)
----------------------(^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^)
^change this to your device ^
Remove your account from xcode and sign in again:
Xcode -> Preferences -> 'Acount' Tab Choose your account and tap '-' in the bottom left corner Tap '+' and sign in to your account again Archive
https://i.stack.imgur.com/q0nge.png
As per shown in the picture go to runner and then click on release set your team correctly it will solve your issue thanks
I know it sounds incredible stupid and unbelievable, but what I did to fix it - after 2 hours, was changing my bundle identifier to all lowercase and appending "123" at the end.
This really solved the issue. I don't know why, as I am not a xcode developer. The only thing that mattered was getting it running on a physical device.
https://i.stack.imgur.com/VePR5.png
Success story sharing
cd '~/Library/MobileDevice/Provisioning Profiles/'
(without a backslash before the space between "Provisioning" and "Profiles". I edited the post, so hopefully the correction will show up after peer review.Clean Build Folder
.cd ~/Library/MobileDevice/Provisioning\ Profiles