Posts

Post marked as solved
4 Replies
1.4k Views
My app has a Siri Shortcut that works fine when I execute it from the Shortcuts app on my watch, but if I try to activate it by voice, Siri says: "Sorry, something's wrong. Please try again." and then a second later says "We've had a problem. Please try again." I'm currently on watchOS 8 beta 6. I last tested this in early July with beta 2 or beta 3 and it was working at that time. I haven't made any changes to the intent extension since then. The shortcut activates fine by voice on my phone, running iOS 15 beta 6. I'm also able to execute other Shortcuts by voice on my watch. Has anyone else run into this before? Is there a way to debug the intent extension on the watch, so I can see if any of my intent handler code is even being called?
Posted
by jasonmarr.
Last updated
.
Post not yet marked as solved
0 Replies
322 Views
I have a NavigationView based app and I've implemented support for SwiftUI's state restoration using @SceneStorage to remember which detail view the user has open, as described in Apple's documentation. It's working correctly if the relevant row in the List is visible when I launch the app. However, if the relevant row is initially scrolled offscreen, the detail view doesn't get pushed until I scroll down so that the row is onscreen. I see the same behavior in Apple's sample app, which uses a LazyVGrid (I had to add some additional data to the products.json file such that the main content view had to scroll). Restoring the detail view when the row is offscreen does work in both my app and in Apple's sample app if I replace the List / LazyVGrid with a plain VStack. Is this a known limitation of SwiftUI's state restoration with List and the lazy stack / grid views?
Posted
by jasonmarr.
Last updated
.