You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is related to #86 (which is unmerged due to #102).
That PR gets a Siri Shortcut working with ExampleApp. Siri displays the custom Siri Shortcut UI but fails to display or read out the response text.
The response text for the .success case should be Here is a wild buck.
As I wrote #86, I built the same example Siri Shortcut in a manually managed Xcode project. In that project, the response text is displayed and read out as you would expect. I have tried diff'ing the resulting .app files and can't the culprit. The code for the manually managed example project is here: XcodeExampleApp.zip.
Response text successfully read out in manually managed Xcode project
No response text in Buck-generated Xcode project
I have looked through the console logs of both the working and not working apps using Console.app (filtering for the term "example"). Sometimes (but not always) the broken Buck-built app will print out errors like this:
error 13:16:13.862344 -0700 assistant_service -[AAPIntentsInfoSyncHandler getChangeAfterAnchor:changeInfo:] com.apple.siri.applications: No intents are supported by Intents extensions for com.airbnb.ExampleApp: (
"<LSPlugInKitProxy: 0x7fbb55c4b160> pluginID=com.airbnb.ExampleApp.IntentExtension UUID=FFC456C5-061C-4B6E-B629-26DDA91FF66E version=1.0"
)
I tried changing the bundle identifier for the extensions to be com.airbnb.ExampleApp.ExampleIntentExtension and com.airbnb.ExampleApp.ExampleIntentUIExtension instead of com.airbnb.ExampleApp.IntentExtension and com.airbnb.ExampleApp.IntentUIExtension, respectively. I was curious if the issue was that the last component didn't match the bundle names for each extension. That did not resolve the issue. The full log output for a run of the Buck-built app that printed out that error message is here: sample_console_log_for_02_ExampleApp.txt. In this case the app was built with a Buck-generated Xcode project.
Other potentially useful information:
I have verified that Siri retrieves the response text from the .intentdefinition file in the root of the .app.
The issue occurs identically when building with Buck CLI or a Buck-generated Xcode project.
Code in both the Intent and IntentUI extensions is executing.
I have filed a Radar with Apple including artifacts from both the working manually managed Xcode project and the broken buck-generated Xcode project.
The text was updated successfully, but these errors were encountered:
After merging #103 and rebasing #86 over master, I see and hear text correctly when building and running from both the Buck-generated Xcode project and Buck CLI 🎉
This issue is related to #86 (which is unmerged due to #102).
That PR gets a Siri Shortcut working with
ExampleApp
. Siri displays the custom Siri Shortcut UI but fails to display or read out the response text.The response text for the
.success
case should beHere is a wild buck.
As I wrote #86, I built the same example Siri Shortcut in a manually managed Xcode project. In that project, the response text is displayed and read out as you would expect. I have tried diff'ing the resulting
.app
files and can't the culprit. The code for the manually managed example project is here: XcodeExampleApp.zip.Here are the
.app
files and dSYMs for the working manually managed Xcode project and the broken Buck-generated project: 01 ExampleApp - correct.zip and 02 ExampleApp - no Siri phrase.zip.I have looked through the console logs of both the working and not working apps using Console.app (filtering for the term "example"). Sometimes (but not always) the broken Buck-built app will print out errors like this:
I tried changing the bundle identifier for the extensions to be
com.airbnb.ExampleApp.ExampleIntentExtension
andcom.airbnb.ExampleApp.ExampleIntentUIExtension
instead ofcom.airbnb.ExampleApp.IntentExtension
andcom.airbnb.ExampleApp.IntentUIExtension
, respectively. I was curious if the issue was that the last component didn't match the bundle names for each extension. That did not resolve the issue. The full log output for a run of the Buck-built app that printed out that error message is here: sample_console_log_for_02_ExampleApp.txt. In this case the app was built with a Buck-generated Xcode project.Other potentially useful information:
.intentdefinition
file in the root of the.app
.Intent
andIntentUI
extensions is executing.The text was updated successfully, but these errors were encountered: