Shortcuts: custom AppIntents fail with LN…ActionNotFound

[peterneutron]

Describe the issue

Shortcuts actions that use custom AppIntents fail with LNPerformActionErrorCodeActionNotFound, while the system “Find Virtual Machine” action works.

• Symptom: Adding or running an action connects Shortcuts → UTM, but fetching dynamic parameter defaults/options fails with ActionNotFound.

• Likely root cause: The action’s identifier previously relied on the derived fully-qualified Swift type name. After module/target/type renames, the derived ID changed. Shortcuts still requests the old ID persisted in existing shortcuts; UTM (exposing the new ID) replies “action not found”.

Reproduction steps

1. Use a Shortcut action (e.g. Get Virtual Machine Status).
2. Run the Shortcut or open the action to load its parameter options.
3. Observe the error in Console.

Console excerpt (Shortcuts.app)

[com.utmapp.UTM] Not Connected → Connecting → Connected
Starting operation <LNFetchParameterOptionDefaultValueConnectionOperation …>
Error Domain=LNContextErrorDomain Code=2002 "LNPerformActionErrorCodeActionNotFound"

Expected behavior

• The action loads parameter options (VM list) and returns status.

Actual behavior

• Shortcuts connects to UTM, then fails with ActionNotFound.

Configuration

• UTM Version: 4.7.4 (115)
• macOS Version: 26.0 (25A354)
• Mac Chip: M3 Pro

Proposed fix

• Stabilize identifiers: Add explicit, stable IDs to all custom AppIntents so they no longer depend on module/type names.

[osy]

I'm not sure what you mean by stable id. Are you saying the action worked fine on 4.7.3 but broke when you updated to 4.7.4? How did you install the previous version? How did you install the latest version?

[peterneutron]

Got it to work in a local build, as for your question I used version v4.6.5 without AppIntents before upgrading to v4.7.4 with the release of macOS Tahoe.

[osy]

FYI, your fix didn't work once it was production signed (same error) but I did manage to get it working in the end 5ee79c7

[peterneutron]

Yeah I saw your recent commit, sorry for causing you trouble with this. It did work at the time on my local build though. Just out of interest did you find out why it didn't work when it was production signed?

[osy]

No idea, but I realized that the id string didn't make a difference (I don't think it's consumed anywhere) but I thought you had the right idea so I just did that out of a guess.

[peterneutron]

Appreciate it. I’ll be more careful with my next PR. By the way, Happy New Year!