I have a shortcut on my iPhone 14 Pro Max I use almost daily, where I tell Siri "I'm leaving" and she prompts me with three menu options to set my house alarm to arm home, arm away, or no alarm. Used to work flawlessly, but after updating to 16.4, not anymore.
When I give her a voice answer, the captions will show my reply but nothing else happens. Siri will ask repeatedly over and over until I either exit the shortcut or tap a menu reply on the screen.
I have rebooted, turned Siri off and back on, rebuilt the shortcut from scratch, checked microphone access in privacy, and deleted my Siri dictation history with no joy. Siri will still work for anything I ask (weather, reminders, etc.), but it's only where the shortcut asks for a response and my vocal response is ignored.
I tried the same action on my M1 iPad Pro, also updated to 16.4, and the behavior is the same as my iPhone where Siri will not acknowledge my voice. I have not updated my M1 Pro MBP and the shortcut runs as it should on my Mac.
This looks to me like a 16.4 bug, but I wanted to check around. I searched the 16.4 beta threads and I couldn't find this issue mentioned. I would love to have *just one* iOS 16 release this year that didn't have some annoying bug with it.
When I give her a voice answer, the captions will show my reply but nothing else happens. Siri will ask repeatedly over and over until I either exit the shortcut or tap a menu reply on the screen.
I have rebooted, turned Siri off and back on, rebuilt the shortcut from scratch, checked microphone access in privacy, and deleted my Siri dictation history with no joy. Siri will still work for anything I ask (weather, reminders, etc.), but it's only where the shortcut asks for a response and my vocal response is ignored.
I tried the same action on my M1 iPad Pro, also updated to 16.4, and the behavior is the same as my iPhone where Siri will not acknowledge my voice. I have not updated my M1 Pro MBP and the shortcut runs as it should on my Mac.
This looks to me like a 16.4 bug, but I wanted to check around. I searched the 16.4 beta threads and I couldn't find this issue mentioned. I would love to have *just one* iOS 16 release this year that didn't have some annoying bug with it.
