This is still a problem for me in Xcode 16.2 running Sequoia 15.1.1. It's been an ongoing bug for a while now and I can't set the right fonts.
Does Apple not care that we can't deliver apps like this? Will we have to programmatically set the font for every single control? Surely, this can't be that difficult to fix. Why is this so low on their radar? This post is 18 months old now. Too busy faffing about with AI to get the basics right!
Rowan_P_D
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
From
Sydney, Australia
Post
Replies
Boosts
Views
Activity
This is still a problem in Xcode 16.2 - in that custom fonts do not appear in the list. I had them briefly working when I upgraded macOS but they didn't work from the next day. The fonts appear in FontBook, they validate in FontBook, I've added the TTFs to Xcode, I've listed the fonts in info.plist (with .ttf extensions), the Copy Bundle Resources list the files. However, but it's Storyboard that doesn't list them.
Why is Apple trying to add "AI" features when stuff like this is listed as a "known issue" release after release?
We really need custom fonts to work please. Would be greatly appreciated.