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
isAssistantOnlyproperty? - 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!