Thanks for the tips. When I select my "SiriIntentsWatchExtension" scheme with "Apple Watch Series 6 via iPhone 12 mini" as the destination I get the following error message when I try to run: "iPhone 12 mini cannot run SiriIntentsWatchExtension. SiriIntentsWatchExtension's architectures (armv7k, arm64_32) include none that iPhone 12 mini can execute (arm64e, arm64v8, arm64, armv8)." It seems like it's trying to execute the extension on the phone instead of the watch. I'll try setting up some logging to see what I can find.

It appears my code is not being called and I filed FB9541952. Thanks!

I just updated the bug to mention that activating the shortcut by voice works fine on watchOS 7, so it seems to be a regression with watchOS 8.

I just verified this is still not working in watchOS 8 beta 7.

I verified this is still not working in watchOS 8 RC and there have been no comments from Apple in my Feedback Assistant report.

Yes! Thank you! That did the trick. I was just looking and can't find that documented anywhere, but I do see that's how the Soup Chef Shortcuts sample project is configured. https://developer.apple.com/documentation/sirikit/soup_chef_accelerating_app_interactions_with_shortcuts I don't see a dedicated documentation page for implementing Shortcuts on the Apple Watch, so I think I'll file a bug report saying this information should be added to this page in the documentation: https://developer.apple.com/documentation/sirikit/adding_user_interactivity_with_siri_shortcuts_and_the_shortcuts_app

Thanks. I played around with the backgroundView property and it does get sized correctly. However, it's a completely static view, so you lose out on the collection view's bounce effect, which ideally I'd like to keep.

Thank you, I just filed FB13299649. Please let me know if you need any additional information.

@Rincewind I'm running into this issue as well and verified it still occurs in iOS 17.2 beta 4.

Thank you for the response. Yes, I'm able to adjust the destination index path in tableView:performDropWith:, so that the item is added in the correct location. However, as far as I can tell, it's not possible adjust the destination index path during the drag, which means the gap shown as the user drags up and down the table view does not correspond to where the row will actually be added when the user drops. If that's not possible, let me know and I'll file an enhancement request.