#ShortcutsApp on #macOS 14.4.0 not giving a shit about what I set in my app’s actions and just reporting the default value is a nice touch. I clearly remember it working fine on 14.3.
I'm finally learning about using App Intents for implementing configurable options for widgets. After watching the WWDC videos one thing is not clear to me.
If my app does not have any configurable widgets, and therefore does not have a custom intent file, can I keep using those widgets "as is" and then just create a new widget that uses App Intents for the widget's options?
I’m still experimenting with AppShortcuts and noticed an issue with localization:
When I use a LocalizedStringResource with an actual key like shortcuts.markhabit.shorttitle instead of the default value for the AppIntent's shortTitle, the App Shortcut will show this key in the Shortcuts app instead of the provided defaultValue.
I was expecting it to be displayed using the default value. Am I holding it wrong?
People using #CoreData / #SwiftData with #AppIntents for Siri/shortcuts/widgets/focus: have you made your models (say CDItem) conform to AppEntity or have you created another “lightweight” type that maps to your model (ItemEntity)?
What’s the smart way to implement that?
In the Backyard Birds project, Apple creates another type to use in intents. But when I do that, I find myself duplicating code in both types.
#AppIntents heads-up: DynamicOptionsProvider comes out differently when compiling with #Xcode 15 compared to 14.3.1.
The resulting list looks different in the Shortcuts editor but, more importantly, its filtering doesn't work. Enter any text and you'll get zero results. 😐
How do AppIntents mesh with NSUserActivity? I’m creating app shortcuts that do the same thing, seems like almost a direct replacement. I’ll seemingly need to turn off isEligibleForSearch and isEligibleForPrediction, and remove suggestedInvocationPhrase. But I see no way to indicate app intent relevance like you do by setting userActivity. I'll continue to set a user activity to utilize isEligibleForHandoff but that's it. Does that sound right? #iosdev#appintents
When you convert a legacy Siri intent to an AppIntent, it generates AppEntity structs from the legacy intent types. And there is backwards compatibility support by means of CustomIntentMigratedAppIntent and consistent use of property names and types.
I'd like to rename my AppEntity structs. Does the name of the AppEntity structs matter, or can I rename them?
Just listening to the “iPadOS 17 Wishes” @appstories episode and must say that @viticci’s suggestion for Spotlight extensions would make me so happy 🥹
Maybe as be part of #Shortcuts / #AppIntents without even (much) extra work to be done by devs? Essentially “just” expose intents in Spotlight with a more interactive UI, allowing to directly type in parameters (Raycast-style) and other kinds of rich interactions without leaving #Spotlight? 🤔