Migrating legacy intents to AppSchema

Any guidance for migrating legacy AppIntents that are nearly identical in functionality to AppSchema app intents? I want to avoid duplicate intents (old vs new) showing up in Shortcuts.

Answered by Frameworks Engineer in 891944022

You may find it possible to conform your existing intent to a schema if all of the required parameters already overlap with your existing parameters. Are the two versions wildly different?

I ran into this last year. If you're struggling to conform your existing App Intents, I believe you can throw this flag on the duplicate ones to keep them hidden from Shortcuts.

https://developer.apple.com/documentation/appintents/assistantschemaintent/isassistantonly

I should add that I realize that it is possible to avoid the duplication in Shortcuts by marking the new intents as "AssistantOnly", but that is not great because would force Shortcuts users to stay on the legacy AppIntents. The best would be a migration mechanism to convert any automations the user set up to make them use the new AppSchema intents. Is that feasible?

You may find it possible to conform your existing intent to a schema if all of the required parameters already overlap with your existing parameters. Are the two versions wildly different?

Interesting idea. The AppSchema intents have an additional parameter.

Migrating legacy intents to AppSchema
 
 
Q