Conflict between capability User Assigned Device Name & Contacts notes entitlements

PLATFORM AND VERSION iOS Development environment: Xcode 15.4, macOS 14.1.1 Run-time configuration: iOS iOS 17.4.1,

There are two ways that Apple grants access to managed capabilities. In my Using the Multicast Networking Additional Capability I label these as the old process and the new process. To help you out here I need to know which process you’re using for each of these capabilities:

• It sounds like User Assigned Device Name is using the new process. Please confirm?

• And what about Contacts Notes?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Hi Thank you for the response. Please find the updates below.

• 1. It sounds like User Assigned Device Name is using the new process. Please confirm? Yes you are right the User Assigned Device Name capability added in to our App ID and then create a provisioning profile based on that. ie, new process.
• 1. And what about Contacts Notes? ** Contacts Notes added additional capability to our provisioning profile** ie, the old process

Thank you.

Interesting. Those should be compatible [1]. The basic idea would be:

1. Set the User Assigned Device Name additional capability on your App ID.

2. Then create a provisioning profile from that App ID.

3. And, while doing that, apply the Contact Notes template to the profile.

Some notes:

• This involves the old process, and the old process requires that you use manual code signing.

• One or both of these might be restricted to specific App IDs.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] In general:

• Two old process managed capabilities are not compatible.

• All other combinations are.

Hi Team,

As you suggested we have created the provisioning profile for the User Assigned Device Name capability enabled App Id and then applied the Contact Notes template to the profile. Still getting the same error "Provisioning profile "IDriveOnlineBackUp_Dev2" doesn't support the User Assigned Device Name capability."(performing manual code signing)

Here Im attaching the screenshots of error, entitlement plist and the build settings User-Defined provisioning profile settings. Please check those let me know if anything missing. Also let me know if there any additional build settings we have to take care on this scenario.

We have another application called IDrive 360 which also provides similar services to the customer. 360 application as well we have the above mentioned capabilities ie, "User Assigned Device Name" & "Contacts notes Field access' '.

Here the difference is 360 having both of these capabilities as a part of the App ID(New Process). The provisioning profile showing Entitlements as default. We are able to Debug/Achieve the target without any issue.

Kindly consider this point.

Thanks & Regards

Hi , Could you please provide me an update on the above.

Thanks & Regards

I’ve been researching this internally but haven’t yet found any actionable results.

It’d help if I knew the Team ID for these products. Are you happy to post that here?

If not, that’s cool. Just reply here confirming that and I’ll suggest an alternative path forward.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Really sorry as per the company policy we cannot share the information with the public. Can you please check if possible further discussion through email? We already had multiple conversations with the technical team and were not getting proper response but at least it's getting here.

Thanks & Regards

we cannot share the information with the public.

Not a problem [1].

I suggest you submit a code-level support request so that I can get your Team ID from there. Once I have that information, we can continue the discussion here in the forums. When you create the request, indicate that you were referred by someone at Apple and make sure to include a link to this thread.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] Although note that your Team ID is not super sensitive, in that’s embedded into every app that you ship (-:

Hi,

Actually we have already raised a code level support request with Case-ID: 7747625. There the person who connected suggested posting the query on the developer forum for further discussions. Can you please collect the information from the existing request(Case-ID: 7747625).?

Thanks & Regards

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"

Hi

Thanks for the above .

It seems there is again confusion arises on the statement “the difference is 360 having both of these capabilities as a part of the App ID (New Process).” Actually this IDrive 360 app is entirely a different app and I just mentioned there to specify that with the new process everything is working fine without any issue. But the actual problem is with the "IDrive Online Backup" app as it is following old process for " Contacts notes entitlements" & new process for "User Assigned Device Name" . Could you please have a look. Thank you

Hi Team,

Could you please provide an update on this? We are currently unable to proceed with the resolution.

Hi Team,

Still waiting. Kindly consider.

Thank you.

It would help if you used redacted App IDs rather that product names. It’s hard for me to understand the mapping between the two.

Which App ID is causing your problems?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Hi Team,

Sure, Please check the redacted App Id of IDrive Online Backup that we are facing the issue below.(Combined old and new process)

`5_ _ _ _ _ _ _ _ _.c_ _.p_ _ _ _ _ _ _ _ _.i_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
`

• User Assigned Device Name capability added in to our App ID and then create a provisioning profile based on that. ie, new process.

• Contacts Notes added additional capability to our provisioning profile** ie, the old process

And below is the app id(of IDrive 360) that working perfectly fine with the "User Assigned Device Name" & "Contacts notes Field access' entitlements both completely on new process.

2_ _ _ _ _ _ _ _ _.c_ _.i_ _ _ _ _.i_ _ _ _ _ _ _ _

Please check and let us know.

Thanks & Regards

OK, let me start by reiterating a point I made earlier: Based on my conversation with the DTSer who supports this feature, Contacts Notes Field Access has transitioned from the old process to the new process. That means the old process is no longer relevant and you should ignore it.

With regards App ID 5_________.c__.p_________.i_________________, it’s in the allowlist for User Assigned Device Name but not for Contacts Notes Field Access. You won’t be able to use the latter for that App ID. If you need to do so, you will have to get back in touch with the folks who manage that capability and ask them to add that App ID to your team’s allowlist.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Hi ,

It appears that we can no longer proceed with the old process as the additional capability for Contact Notes is no longer functioning(old process ie, added capability to our provisioning profile).

In our AppId settings, we cannot find the Contact Notes capability to request its addition (please see the attached screenshot for reference).

Previously, we submitted a request and had the Contact Notes capability approved without any direct interaction with an Apple representative.

Could you please assist us in approving the Contact Notes capability under our AppId?

Thank you for your help. Best regards,

Could you please assist us in approving the Contact Notes capability under our AppId?

No. I’m not involved in the approval process for this capability. I recommend that you follow the path that you previously followed.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"