Post

Replies

Boosts

Views

Activity

Reply to Prevent Xcode from injecting UIRequiredDeviceCapabilities
Okay, this is… not fun. I've stripped the key out, and now App Store Connect doesn't even allow the upload any more. Invalid Bundle. Your binary, 'foo.bar', has a 64-bit architecture slice, so you must include the "arm64" value for the UIRequiredDeviceCapabilities key in your Xcode project. Learn more (https://developer.apple.com/library/content/documentation/General/Reference/InfoPlistKeyReference/Articles/iPhoneOSKeys.html#//apple_ref/doc/uid/TP40009252-SW3) So I must include it, but I also may not include it. How do I resolve this?
Jan ’25
Reply to Selecting an output language with Foundation Models
I've tested The user's locale is de. as the first sentence, but this was completely ignored and the output was in English. By contrast, The output must be in German. worked. I've filed FB18970592 to ask for an API that allows to set the output locale. I guess we're not the only ones that want an output in a different language, and avoiding prompt engineering is the exact point why @Generable exists. In the same spirit, hopefully there's going to be an API to reliably set the output language.
Jul ’25
Reply to UITabBar ignores font in iOS 26.2
Hi Albert, thanks for the response. The Avenir Next font is included in iOS since forever (iOS 6?), so no need to declare it using the UIAppFonts key. I tried configureWithOpaqueBackground, it didn't make a difference. I've file FB21291879 and have attached a small demo project and screenshots there. It's pretty simple: use a default UITabBar and in viewDidLoad, change the appearance: self.tabBar.standardAppearance.compactInlineLayoutAppearance.normal.titleTextAttributes = [ .font: UIFont(name: "AvenirNext-DemiBold", size: 28.0)! ] Run it on iOS 26.0. or 26.1 and the tab bar renders with a large font. Run it on iOS 26.2 and the font is a small San Francisco.
Topic: UI Frameworks SubTopic: UIKit Tags:
Dec ’25
Reply to 26.4 RC documentation omits Foundation?!
Yep, seeing the same thing. There's a lot of other stuff broken with Xcode 26.4. For example, the Swift symbol NSTextAttachment.character is gone and we have to use NSAttachmentCharacter which in turn produces an error when compiling with Xcode 26.3 and earlier. (FB22341879). And then there's the broken Claude Agent support which forces you to re-login every few hours. Paired with the fact that macOS 26.4 cannot run Address Sanitizer builds from Xcode 26.3 and earlier, and you thus HAVE to use Xcode 26.4, I'm very frustrated with Apple's software quality right now.
Apr ’26
Reply to Prevent Xcode from injecting UIRequiredDeviceCapabilities
Okay, this is… not fun. I've stripped the key out, and now App Store Connect doesn't even allow the upload any more. Invalid Bundle. Your binary, 'foo.bar', has a 64-bit architecture slice, so you must include the "arm64" value for the UIRequiredDeviceCapabilities key in your Xcode project. Learn more (https://developer.apple.com/library/content/documentation/General/Reference/InfoPlistKeyReference/Articles/iPhoneOSKeys.html#//apple_ref/doc/uid/TP40009252-SW3) So I must include it, but I also may not include it. How do I resolve this?
Replies
Boosts
Views
Activity
Jan ’25
Reply to Prevent Xcode from injecting UIRequiredDeviceCapabilities
Have reported this via Feedback: FB16441258.
Replies
Boosts
Views
Activity
Feb ’25
Reply to Selecting an output language with Foundation Models
I've tested The user's locale is de. as the first sentence, but this was completely ignored and the output was in English. By contrast, The output must be in German. worked. I've filed FB18970592 to ask for an API that allows to set the output locale. I guess we're not the only ones that want an output in a different language, and avoiding prompt engineering is the exact point why @Generable exists. In the same spirit, hopefully there's going to be an API to reliably set the output language.
Replies
Boosts
Views
Activity
Jul ’25
Reply to UITabBar ignores font in iOS 26.2
Hi Albert, thanks for the response. The Avenir Next font is included in iOS since forever (iOS 6?), so no need to declare it using the UIAppFonts key. I tried configureWithOpaqueBackground, it didn't make a difference. I've file FB21291879 and have attached a small demo project and screenshots there. It's pretty simple: use a default UITabBar and in viewDidLoad, change the appearance: self.tabBar.standardAppearance.compactInlineLayoutAppearance.normal.titleTextAttributes = [ .font: UIFont(name: "AvenirNext-DemiBold", size: 28.0)! ] Run it on iOS 26.0. or 26.1 and the tab bar renders with a large font. Run it on iOS 26.2 and the font is a small San Francisco.
Topic: UI Frameworks SubTopic: UIKit Tags:
Replies
Boosts
Views
Activity
Dec ’25
Reply to 26.4 RC documentation omits Foundation?!
Yep, seeing the same thing. There's a lot of other stuff broken with Xcode 26.4. For example, the Swift symbol NSTextAttachment.character is gone and we have to use NSAttachmentCharacter which in turn produces an error when compiling with Xcode 26.3 and earlier. (FB22341879). And then there's the broken Claude Agent support which forces you to re-login every few hours. Paired with the fact that macOS 26.4 cannot run Address Sanitizer builds from Xcode 26.3 and earlier, and you thus HAVE to use Xcode 26.4, I'm very frustrated with Apple's software quality right now.
Replies
Boosts
Views
Activity
Apr ’26