We are developing an application for local file discovery and transfer.
We applied to Apple for two permissions. One is com.apple.developer.networking.multicast, which supports the four provisioning profiles: Development, Ad hoc, App Store Connect, and Developer ID. The other is com.apple.developer.device-information.user-assigned-device-name, but Apple only approved it for Development and Ad hoc, without granting App Store Connect support. This prevents us from using the user-assigned-device-name permission in the archive.
Could you please clarify the situation? How can we get user-assigned-device-name supported for App Store Connect?
I’m not involved in the approval process for this capability, so I can only talk about this in general.
It’s not uncommon for additional capabilities to be granted just for development [1]. In most cases you’re notified of that limit when you’re granted the capability, along with information about how to apply for the capability to be extended for distribution. If that didn’t happen in this case, my suggestion is that you get back in touch with the approval folks.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
[1] I even have a post, Finding a Capability’s Distribution Restrictions, that explains how to confirm this.
