We have requested an additional capability called "User Assigned Device Name" for my application to Apple and got approved the same on for debug/adhoc/release environments . Since then we are facing issues on code signing. We are always getting the compiler error "* Provisioning profile "xxxxxxxxxxx" doesn't support the User Assigned Device Name capability." on both Debug and Release environment.
There is another capability "contacts notes entitlements" that we got approved long back when it was not apart of Apple ID(additional capabilities) rather we got approved as a part of our provisioning profile.
Suppose we removed "contacts notes entitlements" from the profile and deleted it from the entitlement folder the project compiled without any error. So we are strongly believes the conflicts on the "contacts notes entitlements" is the root cause.
We are about to release the version and which is blocked due to this error. So kindly look in to this issue and do the needful asap.
STEPS TO REPRODUCE Added user assigned device name capability from Signing & Capability Tab in project in settings.
Added the team, valid provisioning profiles and try to sign in manually.
Getting the error “Provisioning profile xxxxxxxxxxxx" doesn't support the User Assigned Device Name capability." Note: Already got approval for the “user assigned device name” . Which is listed under the app id.
Can you please collect the information from the existing request (Case-ID: 7747625)?
Yep, that works for me!
Looking at your team I see that you have both User Assigned Device Name and Contacts Notes Field Access set up as additional capabilities. That’s good, because it means you’re using the new process for both. So, we can ignore the old process stuff. Sorry about that distraction.
One important thing to note here is that both of these additional capabilities have App ID restrictions. That is, you can only use them for specific App IDs:
-
User Assigned Device Name is limited to:
5_________.c__.p_________.i_________________L_________.c__.p_________.i______.i______2_________.c__.i_____.i________
-
Contacts Notes Field Access is limited to:
J_________.c__.i_____.i________2_________.c__.i_____.i________
Note I’ve redacted all but the first letter of the each App ID element to avoid revealing too much info. I’ve kept the length of the element the same, which should let you work out which is which.
The only App ID that has both additional capabilities is 2_________.c__.i_____.i________. That gels with your earlier statement that “the difference is 360 having both of these capabilities as a part of the App ID (New Process).”
My takeaway from this is that:
-
The old process stuff is now defunct and you should just ignore it.
-
If you need to use Contacts Notes Field Access for an App ID other than the ones listed above — based on your DTS case I think the App ID in question is
J_________.c__.p_________.i_________________— you’ll have to apply for your access to be extended.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
