Accented application name is not recognized in App Shortcuts phrases

Question

brebispanique OP

Created 8h

Replies 3

Boosts 0

Participants 4

Hello,

I am trying to set up App Shortcuts with App Intents in my app, which has an accent (é) in the name.

It seems that with an accented application name (e.g. "Démo"), shortcuts phrases are not recognized by Siri or with the "App Shortcuts Preview" tool in Xcode.

public struct DemoAppShortcuts: AppShortcutsProvider {
    public static var appShortcuts: [AppShortcut] {

        AppShortcut(
            intent: OpenDemoIntent(),
            phrases: [
                "Find the tests in \(.applicationName)",
            ],
            shortTitle: "Find tests",
            systemImageName: "location"
        )
    }
}

With Siri, when saying the phrase "Find the tests in Démo", the shortcut is not launched

I tried with the "App Shortcuts Preview" tool in Xcode, it does not match any Intent. (see screenshot)

I set up App Name synonyms as a workaround but it seems to not always work.

Has anyone encountered this problem ? Is there any other workaround ? Is this a bug with iOS 27 / Xcode 27 ?

I filed a feedback FB23791964 with an Xcode Project

Answer 1

Claude31 OP

7h

It is not the first time iOS has problems with accented words.

I had a problem with UIActivityViewController failing to Airdrop if filename has an accented char. FB22253128

Answer 2

Etresoft OP

6h

Don't put anything other than ASCII in your app name, Xcode project, or any other file.

If you want localized names for things, use the appropriate Info.plist keys or other localization tools.

Answer 3

DTS Engineer OP

Apple

5h

Thank you for this very interesting post.

App Shortcuts phrase matching when the app's name (the value substituted for \(.applicationName)) contains diacritics/accented characters the phrase-matching engine used by both Siri and the App Shortcuts Preview tool in Xcode has trouble tokenizing/normalizing accented names like "Démo." You've already found the two workarounds. Not always fold/normalize accented Latin characters (é → e) consistently between what the speech recognizer outputs and what the grammar expects, and sometimes fail to generate a spoken-form variant for the accented string at all, so "Démo" never gets a matching phonetic entry.

Test with a non-accented CFBundleDisplayName temporarily to confirm the diagnosis, if phrases suddenly match reliably with "Demo" instead of "Démo," that isolates the accent as the cause definitively but sounds like you may have already effectively proven this.

May I ask you to try something as well? Can you try to provide this API with OpenIntent https://developer.apple.com/documentation/appintents/adopting-app-intents-to-support-system-experiences and see if you get another result? Would you be able to update the thread and we can take it from here.

Thanks

Albert  WWDR