App Intents not discovered by iOS 16 Beta 1

Question

AlexSFD OP

Created Jun ’22

Replies 7

Boosts 2

Views 2.5k

Participants 9

Hi,

I tried to implement the new AppIntents to replace some old shortcuts. I followed the sessions and their examples on how they are implemented. Unfortunately, I have not been able to get an App Intent into the Shortcuts App.

I tried it on different apps, new projects and tried multiple changes to the intents. Is there something that I'm missing or is this just a bug in Beta 1?

Here's my sample code:

import AppIntents

struct TestIntent: AppIntent {

    static var title: LocalizedStringResource = "Test"

    static var description: IntentDescription? = IntentDescription("Test description")

    

    func perform() async throws -> some IntentPerformResult {

        .finished(value: "Test")

    }

}

I filed a feedback for this issue: FB10102293

All the best,

Alex

Boost

Answer 1

Jad-T OP

Jun ’22

Hello It's not working for me either.

0

Answer 2

Jad-T OP

Jun ’22

I also tried implementing the SiriTipView(intent: AddDataIntent()) in one of my views in SwiftUI, however I can't see it.

0

Answer 3

mehulFunnmedia OP

Jun ’22

Have you implemented AppShortcutsProvider protocol?

0

Answer 4

ajlewis OP

Jun ’22

I'm having the same issue, and I have implemented the AppShortcutsProvider protocol.

0

Answer 5

tgpeter07 OP

Aug ’22

My app intents were working, no change, and then they stopped working with no code changes. Incredibly fragile feature.

0

Answer 6

nachojackson OP

Aug ’22

I'm finding that while my intents work when manually triggered through the Shortcuts app, the Siri feature simply isn't working. I can type my exact app intent phrase and it simply doesn't pick it up.

In addition, it seems like both the ShortcutsLink and SiriTipView are busted. Both of them display placeholder text.

App Intents seem to be very unwell. Given how close to GM we must be, it's pretty disappointing.

1

Answer 7

Engineer OP

Apple

Sep ’22

Hi, this is a known bug and should be fixed in an upcoming release.

0