We have a list app that implements INAddTasksIntent so users can add items to our app with Siri. We're now working on implementing an App Intent for the .reminders.createReminder schema for iOS 27. Our app still supports iOS 18, so it implements both INAddTasksIntent and the .reminders.createReminder schema. Observed behavior (iOS 27 beta 4): When we say "Siri, add eggs to my grocery list in AppName", Siri routes the request to the legacy INAddTasksIntent handler in our SiriKit extension. Our new CreateReminderIntent is never invoked. I confirmed this with breakpoints and logging in both handlers. The CreateReminderIntent does seem to be set up correctly, because it appears in the Shortcuts app and I can invoke it via AppIntentsTesting. Also, after using the above phrase, I was able to say "Siri, add cookies to my grocery list" and the item got added to my app via the INAddTasksIntent, even though I didn't specify the app name in the request. This also worked with a version of our app that does not contain CreateReminderIntent running on iOS 26.5. Isn't the app name normally required for INAddTasksIntent to be invoked? Questions: Is Siri activating the INAddTasksIntent instead of the new CreateReminderIntent expected behavior? Are users on iOS 27 going to have a worse experience adding items to our app with Siri if we support both INAddTasksIntent and the new CreateReminderIntent? If so, how do you recommend we proceed? Thank you for any guidance you can provide.

I've adopted the .reminders.createReminder schema so users can create reminders in my app via Siri and Apple Intelligence. My app only supports a subset of the schema (title, list, and note), but the macro requires me to declare all the other parameters (e.g. isFlagged, tags), so I declare them and ignore them in perform(). The problem: in the Shortcuts app, every declared parameter shows up as an editable field, so it looks like my app supports flags, tags, etc when it doesn't, and the values are silently ignored if the user sets them. Is there a supported way to keep parameters my app can't fulfill from appearing in Shortcuts while still conforming to the schema? The best workaround I've found is to mark the schema intent isAssistantOnly = true (which hides it from Shortcuts while keeping it available to Siri/Apple Intelligence), and then use AppShortcutsProvider to provide a separate non-schema AppIntent that exposes just title/list/note to Shortcuts. However, the docs describe isAssistantOnly as a migration aid that's only intended to be enabled temporarily while migrating an existing intent to an app schema intent. Questions: Is that a supported use of the isAssistantOnly property? Is there a way to mark individual parameters as unsupported so they do not appear in Shortcuts? Is there another recommended approach when an app can only fulfill part of a schema? Thank you!

I've added NSAlarmKitUsageDescription to Info.plist and InfoPlist.xcstrings. The localized string is being used when I run the app, but Xcode is marking the string as "stale" in InfoPlist.xcstrings. This doesn't occur for any of the other UsageDescription strings in our app, such as NSPhotoLibraryUsageDescription and NSSiriUsageDescription. This occurs in both Xcode 26.2 and Xcode 26.3 RC. Is this a known issue? Should I just mark the string as being managed "Manually" instead of "Automatically" to make the warning go away?

We are seeing a kernel panic in nfsd when using vagrant synced folders. The issue started with macOS 15.4 and still occurs with macOS 15.5. It’s 100% reproducible when bringing up a new vagrant environment. The kernel panic does not occur when using smb instead of nfs. https://developer.hashicorp.com/vagrant/docs/synced-folders/nfs Other people have reported a similar issue when using nfs with Docker. https://github.com/docker/for-mac/issues/7664 I filed this under FB17853906. I spoke with an engineer at the Apps & Services WWDC lab and they recommended I post here to make sure the bug gets looked at and routed to the correct team.

When reordering items within a table view, I can use tableView:targetIndexPathForMoveFromRowAtIndexPath: to adjust the destination index path. Is there a way to adjust the destination index path when dropping onto a table view if the drag was initiated in a different view? For example, if I'm dropping an object into a table view where the rows are sorted alphabetically, I want the gap to appear in the location where the item is going to end up, regardless of which row the dragged item is being dragged / dropped at.

If Autocorrect is showing a potential correction, sometimes tapping elsewhere in the UI causes the suggestion to be accepted, but the touch event is not passed to the tapped view. A screen recording from a sample app demonstrating the issue is available here. I first type "Coffee", which does not show an autocorrect suggestion and then I tap on a table row, which successfully shows an alert. I then type "Coffeesc", which shows an autocorrect suggestion. Then when I tap on one of the table rows, the autocorrect suggestion is accepted, but our implementation of tableView:didSelectRowAtIndexPath: is not called and no alert is shown. The issue began in iOS 17.1 and only occurred when the Predictive Text switch in Settings -> General -> Keyboard was OFF. However, the issue still occurs in iOS 18 beta 3 and now I'm able to reproduce the issue when the Predictive Text switch is ON. I filed FB13418977 about the issue back in November (including the sample project shown in the video that reproduces the issue), but there have been no comments from Apple in the bug report. I initiated a code-level support request in April, but was told DTS did not have a workaround and that I should just continue to follow the bug report for updates. This bug impacts the primary text field in our app, but since Predictive Text is enabled by default, it hasn't impacted a large number of our customers on iOS 17. And for users that were impacted, we were able to tell them to enable Predictive Text as a workaround until the bug is fixed. With the issue occurring even when Predictive Text is ON in the iOS 18 betas, the text field is now nearly impossible to use. The only workaround I can think of is turning off autocorrect for that text field, but that isn’t a great solution, as it leads to a significant increase in typos when the user types multiple words. We would desperately like for this to be fixed in iOS 18, but if someone at Apple could please look at FB13418977 and at least provide us with an update or potential workaround, it would be greatly appreciated. Thank you and please let me know if you need any additional information.

In our most recent app update, we added a WidgetKit extension to our watch app. The WidgetKit extension has a minimum deployment target of watchOS 9, but the watch app has a minimum deployment target of watchOS 7. After releasing this update, we discovered customers running watchOS 7 & 8 can no longer install the app on their watch. When tapping the Install button in the Watch app on the phone, it spins for a while and then stops and returns to saying Install. No error message is displayed. If I build and run the iOS app through Xcode, I'm able to install the app on a watch running watchOS 8.8.1. However, I'm unable to install the app on the watch from TestFlight or the App Store. Has anyone else run into this or have any thoughts on what project settings we should look at to fix the issue?

My app has a Siri Shortcut with a single parameter that Siri asks for each time the shortcut is run (built using an intentdefinition file). The shortcut works fine when I execute it from the Shortcuts app on my phone, but beginning with iOS 16.4, when I activate it by voice, Siri prompts me for the parameter and after I respond Siri says: "Sorry, could you say that again?". If I repeat the input, it just does a web search. This issue has been reported to us by several users. I was able to reproduce the issue with the build of our app from the App Store (built with Xcode 14.2) and with a local build of the app created with Xcode 14.3. When I run the intent in the debugger, the resolution method for the parameter gets called with an empty array for the parameter and we return [INStringResolutionResult needsValue]. Then Siri asks for the input and after I respond, Siri says "Sorry, could you say that again?"and the line Program ended with exit code: 15 is printed in the console. Is anyone else running into this? Is there anything else I can do to debug this?

I have a UICollectionViewController inside of a UINavigationController and when the collection view does not contain any data, I want to have a single item that fills the visible area of the collection view. I'm using UICollectionViewCompositionalLayout and thought I would be able to do this with a group / item size that has a fractionalWidth and fractionalHeight of 1.0 like this: let itemSize = NSCollectionLayoutSize(widthDimension: .fractionalWidth(1.0), heightDimension: .fractionalHeight(1.0)) let item = NSCollectionLayoutItem(layoutSize: itemSize) let groupSize = NSCollectionLayoutSize(widthDimension: .fractionalWidth(1.0), heightDimension: .fractionalHeight(1.0)) let group = NSCollectionLayoutGroup.horizontal(layoutSize: groupSize, subitems: [item]) let section = NSCollectionLayoutSection(group: group) let layout = UICollectionViewCompositionalLayout(section: section) However, this does not respect the collection view's safe area insets, so the item is too tall and ends up scrolling: Is there a way to have the fractionalHeight take the collection view's safe area into account or some other way to have a single item that fills the collection view's safe area?

My app has a Siri Shortcut that works fine when I execute it from the Shortcuts app on my watch, but if I try to activate it by voice, Siri says: "Sorry, something's wrong. Please try again." and then a second later says "We've had a problem. Please try again." I'm currently on watchOS 8 beta 6. I last tested this in early July with beta 2 or beta 3 and it was working at that time. I haven't made any changes to the intent extension since then. The shortcut activates fine by voice on my phone, running iOS 15 beta 6. I'm also able to execute other Shortcuts by voice on my watch. Has anyone else run into this before? Is there a way to debug the intent extension on the watch, so I can see if any of my intent handler code is even being called?