Xcode Cloud automatic signing mapping user-fonts+app-usage “Font Enumeration” capability?

Developer Tools & Services Xcode Cloud
JimmyCricket OP
Created
Replies 4
Boosts 0
Views 533
Participants 5

Heyo everyone!

Since Xcode 27 (27.0, 27.1, and 27.2 RC), I have not been able to export builds to the App Store through Xcode Cloud that have app-usage on the com.apple.developer.user-fonts key in the entitlements file.

For some inexplicable reason, it seems as though Xcode Cloud's automatic signing is trying to map to the Font Enumeration capability instead of the other Fonts capability? Since I don't have this, it fails. However, I can archive and export these builds to App Store just fine on my local device using 27.1.

Here is what Xcode Cloud's logs are spitting back:

error: exportArchive Automatic signing cannot update bundle identifier “XXX”.
Automatic signing cannot update your registered bundle identifier to enable Font Enumeration. Update your bundle identifier on https://developer.apple.com/account and then try again.

And ideas or am I alone on this island?

Answered by DTS Engineer in 912687022

Thanks for those bug numbers. Using those I was able to track down an even earlier bug about this, also from a third-party developer, namely FB25289421. That bug is with the right folks, and it certainly does look like Just A Bug™, but I’ve no info to share as to when it’ll be fixed or if there’s a workaround )-:

ps It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits.

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

Replies  4
Boosts 0
Views  533
Participants  5
Pokpong OP

The error is specifically about Font Enumeration, which is different from the normal Fonts capability. Apple says enumeration of all installed fonts needs a separate entitlement request; adding the regular Fonts capability to the App ID may not be enough. If your app only needs the user to choose a font, check whether UIFontPickerViewController can replace enumeration. If you really need to list installed fonts, confirm that Apple approved the Font Enumeration entitlement for this bundle ID and that the matching entitlement is present in the Xcode Cloud archive’s signed entitlements and provisioning profile. A local archive succeeding doesn’t confirm Cloud has the same signing assets. Apple’s font overview explains the distinction: https://developer.apple.com/documentation/technologyoverviews/fonts. If approval is already in place and Cloud still asks to enable Font Enumeration, this looks like an Xcode Cloud signing issue worth filing in Feedback Assistant with the workflow log and request ID.
travis78701 OP

I have the same exact problem. I've submitted a feedback report to Apple, but no response yet.

DTS Engineer OP
Apple
Written by travis78701 in 912094022

I've submitted a feedback report to Apple

What was that bug number?

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

DTS Engineer OP
Apple
Accepted Answer

Thanks for those bug numbers. Using those I was able to track down an even earlier bug about this, also from a third-party developer, namely FB25289421. That bug is with the right folks, and it certainly does look like Just A Bug™, but I’ve no info to share as to when it’ll be fixed or if there’s a workaround )-:

ps It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits.

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