Hi, In my widgets, I use minimumScaleFactor to ensure that my text is readable. In iOS 18.0 beta 6 and iOS18.0 beta 7, my texts suddenly became very small. It seems that minimumScaleFactor acts like if it was applying the given scale value to the text. minimumScaleFactor(0.1) seems to display the text 90% smaller than the text without calling minimumScaleFactor. minimumScaleFactor(0.5) seems to display the text 50% smaller than the text without calling minimumScaleFactor. Is this a bug, of is there an unexpected change in the API ? Edit : I have created FB14890220, in case this message remains unseen.

Hello, I have an iPad app that users are running on their M1 / M2 MacBooks thanks to the "Designed for iPad" feature. Some of them reported to me that the pressed keyboard keys were not recognized. According to my source code, it seems that my custom views (that are set as firstResponder) do not get pressesBegan events. While I could not reproduce this specific problem on my M1 Macbook, I found a strange problem that may be related. My view also supports interaction with game controllers. I found that the emulated controller (which is using the keyboard, when the controller emulation feature of the Designed for iPad app is set to On) has some problems. The valueChangedHandler of the GCExtendedGamepad from the GCGameController is only fired if the app is compiled with the "Requires full screen" option set to On. If Requires full screen is unchecked in XCode, the Emulated Controller is still present in the list of game controllers, but no button callbacks are triggered. Note that a real game controller connected via USB will work correctly no matter how Requires full screen is set. Could there be a focus bug of the keyboard not sending events when the app is not a full screen app (resizable on mac, and multitask on iPad)? Or is there something I can change to avoid this problem? I'm lost.

In an app we can use FileManager.SearchPathDirectory.cachesDirectory (objc:NSCachesDirectory) to store files that could be recreated if necessary (and will be automatically deleted by iOS in cases of low disk memory). For app groups, there is a shared location that is automatically created as soon as we use containerURL(forSecurityApplicationGroupIdentifier:) (objc:containerURLForSecurityApplicationGroupIdentifier) : Library/Caches Is this cache directory (created by iOS) also gets automatically deleted by iOS in cases of low disk memory ? I also have more related questions : does this cache directory size count in the used disk space by the app displayed in the settings app ? is this cache directory (and same question for the top containerURL directory) saved in the cloud backups ? Does anyone have any information about this?

Hi, I submitted a TSI request (3756384) more than 3 weeks ago (Fri, Aug 18). I still have not received a response (other than the automated email confirmation). Is everyone at Apple working on fixing iOS17 bugs, or did my request get lost somehow?

Hi, With iOS17 adding APIs to display and handle HDR images in apps, is the AVAssetImageGenerator supposed to generate CGImages with an HDR color profile (when the AVAsset is an HDR video)? I cannot get it to work, in the simulator or on the device : the colorspace of the CGImage seems to always be kCGColorSpaceModelRGB, no matter how I configure the AVAssetImageGenerator. So the created UIImage is not displayed as an HDR image in a UIImageView (with preferredImageDynamicRange set to UIImageDynamicRangeHigh) Is there another known way to generate an image at a specific time of an AVAsset?

Hi, One user reported me that my app is crashing under macOS Ventura beta 13.3 (22E5230e) After investigation is seems that creating an SKView, either by code (SKView* skView = [[SKView alloc] initWithFrame:self.view.frame]) Or by Storyboards ([SKView initWithCoder:]) Crashes the app immediately. It seems to me that this bug is so visible that I cannot understand how apple managed to release it in a public beta. Anyone having the same problem, or knowing a workaround ? Note : here is my feedback assistant report FB12032892

Hi, In my apps, the recent iOS 16.0 beta 7 (20A5356a) broke the .timer DateStyle property of the Text view, in a SwiftUI widget. In previous OS and beta, Text(Date(), style: .timer) was correctly displaying an increasing counter. In iOS 6.0 beta 7, Text(Date(), style: .timer) does not update anymore, (and is offset to the left). The other DateStyle (like .offset, .relative, ...) seems to update correctly. Anyone noticed that (very specific) problem ?