I have several Swift Data types with a property of type enum. Whenever I've tried to write a predicate returning data objects only of a certain enum case, the compiler throws an error from the macro at build time. (which I don't have handy, sorry...). Is this supported? And if so, how would you write the predicate? @Model public final class AlbumList { // ... public var listType: AlbumListType // ... } public enum AlbumListType: String, CaseIterable, Codable { case listener case dj }

Given the new Voice Control natural language enhancements, is there any change in guidance for how developers use accessibilitylnputLabels? Does providing robust utterance coverage across our views still help tune the new system's NLU?

If your app creates an Apple Intelligence schema conforming App Entity, Siri AI can only reason over the schema defined properties. (see this thread). But as a developer, I can add more optional properties on my App Entity with additional metadata about the entity. If my app contributes these App Entities to Spotlight as indexed entities, is SpotlightSearchTool also limited to reasoning over just the schema defined properties, or are these unrelated concepts? Will these additional optional properties on my App Entity enable a deeper SpotlightSearchTool powered search experience around these entities?

The Keynote/SOTU mentioned that phone hardware wise, only iPhone Air and 17 Pro are getting the highest quality local models. Does this only impact 1st party system features, or does that impact us as well? In other words, will our schema conforming App Intents behave differently on this subset of devices. Or is testing on any Apple Intelligence supported hardware sufficient?

My app is built around music albums. How would I support the utterance "open this in Apple Music" when a user is looking at an album in my app? Is a .userActivity with an associated appEntityIdentifier enough? If my AppEntity had the Apple Music ID in one of it's properties would the system figure it out? Or would I need a transfer representation too? This introduction of IntentValueRepresentation was confusing for me. It seems from the talk that maybe this is required to make this work, but doesn't seem like there is any relevant _IntentValue for my use case.

Say you have an App Entity representing an image. And an app intent that returns it as a value. Is there any way to define a compound transfer representation? For example, if the user wanted to create a Shortcut that sent a message or created a note with the image along with the image title as plain text. Last I attempted this, the system rendered a single compound image with the title baked in underneath the actual image, as opposed to the image followed by a text string underneath it.

For schema conforming App Entities, does the synonyms API on DisplayRepresentation feed into Siri AI's natural language understanding of your app's entities?

At WWDC24, the guidance was that you could extend a schema conforming App Entity beyond its pre-defined shape with optional parameters, but that these would not be understood by Siri. In tandem, there was also CSSearchableItemAttributeSet properties but I don't recall how those were or were not understood by Siri. Could you please help clarify how these two related concepts work together going forward in terms of how entities are exposed across Spotlight, Shortcuts, and Siri.

Is SiriKit now deprecated? And if so, how will that impact INAlternativeAppNames as it relates to app name synonyms in App Shortcuts?

The default VoiceOver behavior is to start at the toolbar and work its way down. In some cases, this feels unintuitive to me. One example - my app persists which Tab you were last on across sessions. But on iOS, the tab bar is at the bottom. Sighted users have immediate context. I explored trying to insert a VO bit on load to announce which Tab is active, but that didn't work well and would sometimes clash with other VoiceOver elements. Any guidance here? I'm not a VoiceOver user, so please let me know if I'm trying to change a default AX behavior that shouldn't be messed with. But I want to make sure a VO user has the right context of where they're being dropped into.

Is there any way to know the exact number of grid items that will fit across before you render your template? I'm currently delivering 7 items to accommodate the largest screen sizes, but on smaller screens 3 of these are wasted per row.

I've found myself chasing my tail trying to programmatically adjust my .navigationTitle in SwiftUI so it doesn't get truncated given various dynamic type classes mixed with various device widths... Any guidance here on how to think about adjusting Ul copy based on AX type size constraints?

Why can't you include a custom toolbar item on the parent view of a Tab? I got around this by inserting a bespoke item at the top of my list template to represent the action that would have gone in the toolbar item, and then on all subsequent child views I display the toolbar item as intended. This works, but it feels a little clunky. Any guidance here? Thanks!

Is it possible to use SSML to provide a VO string in multiple languages. For instance, a label in English, but you want it to speak a phrase within that sentence in Spanish for a proper noun.

Hello, I'm working on a MusicKit based SwiftUI app. I've integrated AirPlay using the AVRoutePickerView like so: struct UIKitAirPlayPickerView: UIViewRepresentable { func makeUIView(context: Context) -> AVRoutePickerView { let routePickerView = AVRoutePickerView() routePickerView.prioritizesVideoDevices = false return routePickerView } func updateUIView(_ uiView: AVRoutePickerView, context: Context) {} } The AirPlay menu appears as expected, and selecting an AirPlay device functions as expected. I'm currently sending audio from my app to a HomePod. However, the state of the AVRoutePickerView does not reflect the playback state. There is no cover art and it says "Not Playing". When my device is locked, my lock screen shows the album art, metadata and AirPlay routing as expected. My app uses the ApplicationMusicPlayer however I encounter the same behavior using the SystemMusicPlayer. Any guidance on how to troubleshoot this? Is there any other way to integrate the system AirPlay picker into my app, or is this my only option? Thank you for reading.