I had the same problem a few months ago.
Failed to create provisioning profile. The app ID "com.xxxx.xxxx" cannot be registered to your development team. Change your bundle identifier to a unique string to try again.
The reason (for me) was that our company had an Apple Developer account for $ 99 (so that we could host our app on the App Store) and $ 299 for Apple Enterprise (so that we could create and privately distribute our own applications )
On the Apple Developer website, we registered our com.MikesCompany.AppName
identifier, which was logged into our developer account for $ 99, because our goal was to sell it through the App Store.
But, of course, when we develop and test our application using our Enterprise Account, Xcode will persistently not use this application identifier in the Provisioning Profile, as it was “already used”.
There are many reasons why I hate Xcode (and look at its rating on the Apple App Store, I’m far from being one), and all this code signing is one of the main reasons ...
Year after year, it just doesn’t improve (even the new Auto Code Signing feature allows you to create versions that obviously won’t work on the device and give you the hopeless and misleading “ AppName cannot be installed at this time
” message) .
In any case, the answer to your question ... make sure that you create your application using a member of the correct group in which your application identifier was created.
source share