iOS 26.5 breaks AppIntents with AppEnums defined in Swift Package

Question

Created May ’26

Replies 1

Boosts 2

Participants 2

For some reason since iOS 26.5, a ControlWidgetButton or a Button in a widget configured with an AppIntent conforming to OpenIntent fails to receive its AppEnum parameter correctly if the intent and enum are defined inside a shared Swift Package.

Tapping the control widget button opens the main application, but it doesn't pass the AppEnum parameter value in, leaving the app on its default screen instead of navigating to the intended view. This was working perfectly in iOS 26.4, where the app would launch and receive the correct enum case from the intent. No code, configuration, or scheme changes were made between the two runs, only the simulator/OS version differs.

Has anyone else run into what seems to be a regression on iOS 26.5?

I filed feedback with a sample project: FB22848510

Answer 1

mojo699 OP

1w

I have the same issues with AppEnum parameter with AppIntent, as it doesn't resolve correctly in 26.5 simulator. It seems to still work with a physical iPhone device.

When my widget button action/ shortcut suddenly stopped working, it took me 8 hours to discover that the 26.5 simulator was causing the issue after Xcode and simulator upgrade. I redownloaded the old 26.4 simulator and got it working again. If anything was changed with AppEnum in 26.5, it's not stated anywhere in the Apple Developer release notes and documentations.

In 26.5 simulator it throws cryptic message in log "Programming error: a caseDisplayRepresentations entry for AppEnum case "to-0.0" was not found. This case will be ignored." What the hell is case "to-0.0", it's certainly not one of mine AppEnum case, I don't know where it coming from. But certainly looks like it's breaking somewhere inside framework within 26.5 simulator.