I stumbled upon this article (Suspending authorization requests) but unfortunately it doesn't cover my "get authorisation status and accuracy authorisation at app launch without prompting the user" use case.

Hello, I tried to use the following command xcrun simctl addmedia booted /Users/axel/Dropbox\ \(Maestral\)/Developer/Skipper/App/Resources/GPX/test.gpx And I got this error Failed to import '/Users/axel/Dropbox (Maestral)/Developer/Skipper/App/Resources/GPX/test.gpx', error [NSPOSIXErrorDomain] 22: The operation couldn’t be completed. File type unsupported. An error was encountered processing the command (domain=com.apple.CoreSimulator.LaunchdSimError, code=133): Multiple errors were returned; see stderr Regards, Axel

Hello, I filed the feedback FB23368633 (Xcode DeviceHub: I can't drag and drop a file to a simulator when using DeviceHub) in June 2026. I used to be able to drag any file type (like CSV, XML, GPX). I would appreciate the ability to do the same in Device Hub by drag and dropping.

Additional informations: It's working fine with SwiftUI on iOS 17 and iOS 18. It's working fine with an equivalent UIKit code on iOS 26 and iOS 27. In my opinion, it's very likely to be a SwiftUI regression. I updated the feedback FB23661327 with these informations. I would love an Apple engineer to have a look at it and fix the issue before iOS 27 ships. Axel

Hello, I took the time to check, it's actually not working starting iOS 26.4. For simulators running previous iOS 26 versions (like 26.3), the app shortcuts can be run and the app intents too. iOS 18.6: ✅ iOS 26.3.1: ✅ iOS 26.4.1: ✅ Shortcuts & intents correctly run but only one suggestion is used to create the shortcuts❌ iOS 26.5: ❌ No shortcuts created. Not possible to run shortcuts or intents. iOS 27: ❌ Same as 26.5. I added the information in the feedback. See this screenshot. Regards, Axel

I'm noticing the same. Can you please tell use where to file Core Spotlight feedback in the Feedback App? I can't find the technology in the drop down. Thank you.

I just tested using an Enum in a SwiftData Query Predicate only works for anyAppleOS 27 & doesn't back deploy when building on Xcode 27 🫤 On anyAppleOS 26 & below, Xcode logs "Query encountered an error: Unsupported Predicate: Captured/constant values of type 'TheEnum' are not supported" @Frameworks Engineer do you think there is any chance to back deploy that to prior OS versions? Thank you.

@Frameworks Engineer thank you for sharing that! Does this only work for the new anyAppleOS 27 and not before (like iOS 17/18/26)? Thanks Axel

Here is mine, filed more than 2 years ago: FB13603810

Hello @Frameworks Engineer @cgontijo, I filed feedback for that in January 2024. Basically, the equivalent to NSExpression functions like sum/average/max/median. https://developer.apple.com/documentation/foundation/nsexpression/1413747-expressionforfunction FB13522377 FB13522406 FB13521724 FB13522412 FB13522411 FB13522401 FB13522382 Feel free to check them. It's blocking me from adopting SwiftData because I can't do any operation on my data set as I have to fetch all objects into memory with SwiftData. Regards, Axel

Hello @DTS Engineer, Thank you for answering. I'll try to explain a little bit more the end result I want. Basically, something like what Apple uses for the "Silent Mode" floating pill/indicator at the top of the screen. Something I could use in my app to indicate success/errors/confirmations when some actions are performed by the user. Let say an action is performed in the SheetContentView, I want to immediately present the indicator while also dismissing the sheet. I dismiss the sheet I want the PillNotificationView to stay visible, on top of everything. So it can't be an overlay/ZStack to the SheetContentView, and it can't be an overlay/ZStack to the MyView. Regarding the code (this does not work as explained above because the PillNotificationView is overlaid to the MyView due to the ZStack) ZStack { MyView() if isPillPresented { PillNotificationView() } } .sheet(isPresented: $isPresentingSheet) { SheetContentView() } I want the view to be presented only once either above everything (no matter if the top view is the SheetContentView or MyView). I hope it makes it more clear. Let me know. Axel PS: This UI: https://github.com/ivanvorobei/SPIndicator an old blog post talking about something similar is https://www.fivestars.blog/articles/swiftui-hud/

Hello, I think it's expected that Transaction.updates is not called (because when a user cancels its subscription, there is actually no new transaction to be pushed to the devices) but I expect Product.SubscriptionInfo.Status.updates to be called (also when a user changes plan from monthly to yearly for example, so we can be informed about the renewal product). This Status.update async sequence is called when I test with Xcode testing (with a configuration file). But this behaviour seems to be different in the Sandbox environment (or it's very very slow to update?). Before publishing the app, I want to be sure my flow is working but having two different behaviours between the Sandbox and the Xcode testing is not helping. Thank you, Axel

Hello, The solution I came up to was: Close Xcode. Remove the hidden folder .swiftpm from the Package folder. I noticed the UserInterfaceState.xcuserstate file in a subfolder of this folder contained some references to the languages (I could find language codes in it like "pt-PT"). Open the package again with Xcode. The languages that weren't translated at all (0% progress) got removed from the string catalog. The other languages where at least one string was translated stayed in the string catalog. I don't think this is ideal but I hope it can help others. Axel

@keewon I'm seeing the same on my side. Some apps seem to be working as expected (like Yelp), but others don't have any screenshots. Have you found a solution?

Presenting a standard sheet works fine. Even if I present 10 sheets on top of the others, it never dismisses all at the same time. Wrapping the FamilyActivityPicker inside a custom View and presenting with a sheet works fine. Definitely an issue with the Screen Time API.