INInteraction always has nil intentResponse

I have an intentsDefinitions-based custom Intent for siri shortcuts. The SiriKit API says I can attach INObjects to my custom response for use in an IntentsUI layer, but this intentResponse always appears to be nil. Is this a bug or am I missing something subtle about when my IntentsUI configureView(for:of:interactionBehavior:context:completion:) is called? The INInteraction passed here always seems to be .unspecified as well, never .success like I think it should.

Up vote post of Procrastin8 Down vote post of Procrastin8
2.4k views
Posted by
Procrastin8
Reply
Add a Comment

Replies

Definitely a bug. We are experiencing the same issue on iOS 12 beta 2. The same code used to work on iOS 12 beta 1.

Posted by
snit-tile
Up vote reply of snit-tile Down vote reply of snit-tile
Add a Comment

Do you have a radar? Otherwise, I will file one. Thanks for the Beta 1 context, too, sounds like it really is a bug that will hopefully be fixed for beta 3.


Update:

I wrote one: https://bugreport.apple.com/web/?problemID=41587951

Posted by
Procrastin8
Up vote reply of Procrastin8 Down vote reply of Procrastin8
Add a Comment

I haven't filed it yet. Yesteday evening was the first time I noticed it had stopped working.

Posted by
snit-tile
Up vote reply of snit-tile Down vote reply of snit-tile
Add a Comment

Did you get any update to the bug report?

Posted by
snit-tile
Up vote reply of snit-tile Down vote reply of snit-tile
Add a Comment

I'm seeing an identical problem with iOS 12 beta 3 (and beta 2). Even the Soup Chef example app is getting a nil intentResponse. I would love to know what's happening... Is this an iOS beta bug? Or is there something that Soup Chef and other SiriKit apps need to do differently in order to get a valid response. I've filed radar 41853609: https://bugreport.apple.com/web/?problemID=41853609


—Chris

Posted by
claurel
Up vote reply of claurel Down vote reply of claurel
Add a Comment

It suddenly started working for me yesterday in beta 3. It might have been something server-side they fixed.

Posted by
snit-tile
Up vote reply of snit-tile Down vote reply of snit-tile
Add a Comment