Xcode not recognizing approved User Assigned Device Name capability in provisioning profile

Hi,

I am experiencing an issue where Xcode displays a "Provisioning profile doesn't support the capability" error for the User Assigned Device Name capability, despite it being approved by Apple and visible in our provisioning profile on the Developer Portal.

Background

We have completed and submitted the required capability request form to Apple for the User Assigned Device Name capability and received approval. The capability appears correctly in our provisioning profile on the Apple Developer Portal and shows among the enabled capabilities alongside other standard capabilities like In-App Purchase and Push Notifications.

Issue

However, Xcode consistently displays the error message when trying to enable the User Assigned Device Name capability in our project settings, preventing successful builds with this functionality.

Troubleshooting Steps Attempted

We have tried multiple troubleshooting steps including:

  • Regenerating provisioning profiles
  • Performing clean builds
  • Clearing DerivedData
  • Manually installing profiles
  • Adding the com.apple.developer.device-information.user-assigned-device-name entitlement manually to our entitlements file
  • Toggling automatic signing on and off

Environment Details

  • Xcode Version: 16.4 (16F6)
  • iOS Deployment Target: iOS 13
  • Profile Type: Distribution provisioning profile
  • Capability: User Assigned Device Name

Despite the capability being approved by Apple and visible in our provisioning profile, Xcode does not recognize it. This appears to be a synchronization issue between the Apple Developer Portal and Xcode's capability validation system.

Has anyone encountered similar issues with recently approved capabilities, specifically the User Assigned Device Name capability? Could you please provide guidance on how to resolve this capability recognition issue? Any suggestions for resolving this discrepancy between the Developer Portal and Xcode would be greatly appreciated.

Answered by DTS Engineer in 857978022

The majority of issues like this are caused by limitations imposed on the managed capability. For example:

  • You might have been granted it for development only.
  • You might have been granted it for a specific App ID.

See Finding a Capability’s Distribution Restrictions for info on how to investigate the first point.

ps If this is Team ID 2________2, my view of our records shows that:

  • The capability is limited to single App ID, 2________2.n__.r____.a__.
  • And to Development and Ad Hoc distribution, not for the App Store distribution you’d need to actually ship your app on the store.

Share and Enjoy

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

The majority of issues like this are caused by limitations imposed on the managed capability. For example:

  • You might have been granted it for development only.
  • You might have been granted it for a specific App ID.

See Finding a Capability’s Distribution Restrictions for info on how to investigate the first point.

ps If this is Team ID 2________2, my view of our records shows that:

  • The capability is limited to single App ID, 2________2.n__.r____.a__.
  • And to Development and Ad Hoc distribution, not for the App Store distribution you’d need to actually ship your app on the store.

Share and Enjoy

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

Xcode not recognizing approved User Assigned Device Name capability in provisioning profile
 
 
Q