Hello, Our app provides two actions in the Shortcuts app. However, on some devices running iOS 27, neither action appears, preventing users from setting up automations during onboarding. We have not observed this issue on earlier iOS versions. Implementation Both actions conform to LiveActivityIntent, with their corresponding App Shortcuts declared in an AppShortcutsProvider. Both have a required AppEntity parameter, with initial parameter options provided by EntityQuery.suggestedEntities(). We call updateAppShortcutParameters() at app startup and after saving changes to the platform selection. Observed behavior Only some iOS 27 devices are affected. Some affected users report that the actions appear a few days later, but we have not identified what triggers their appearance. Has anyone encountered similar behavior? Is there a known registration or indexing issue, or anything in this implementation that we should investigate? This blocks a key step in our new-user onboarding, so we would greatly appreciate any guidance or workaround. Thank you.

App Intent actions missing from Shortcuts on some iOS 27 devices

Hello,

Our app provides two actions in the Shortcuts app. However, on some devices running iOS 27, neither action appears, preventing users from setting up automations during onboarding. We have not observed this issue on earlier iOS versions.

Implementation

Both actions conform to LiveActivityIntent, with their corresponding App Shortcuts declared in an AppShortcutsProvider.
Both have a required AppEntity parameter, with initial parameter options provided by EntityQuery.suggestedEntities().
We call updateAppShortcutParameters() at app startup and after saving changes to the platform selection.
Observed behavior
Only some iOS 27 devices are affected.
Some affected users report that the actions appear a few days later, but we have not identified what triggers their appearance.

Has anyone encountered similar behavior? Is there a known registration or indexing issue, or anything in this implementation that we should investigate?
This blocks a key step in our new-user onboarding, so we would greatly appreciate any guidance or workaround.

Thank you.