Braille screen input send action broken in IOS 17

By Frank, 22 September, 2023

Forum
Braille on Apple Products

I have upgraded to IOS 17.
Braille screen input at least on my end seems to have suffered as a result. The 3 finger flick up for activating the send action in messages and What'sup no longer works.
Using a 12 pro. I am also wondering if anybody has found a work around.
I use BSI for just about everything, and boy this one just nerfed my day.
To complicate matters, it does not seem to be device specific.
Your thoughts?

Options

Comments

By Magic Retina on Saturday, September 23, 2023 - 13:36

I went into commands in Voiceover and reset several of them to make BSI actually work. Give that a try.

By Jonathan Candler on Saturday, September 23, 2023 - 13:36

Don't know but haven't had this issue at all and been working ever since I upgrated.

By Frank on Saturday, September 23, 2023 - 13:36

Could you please be a bit more specific about which commands you reset?

Thanks.

By Jo Billard on Saturday, September 23, 2023 - 13:36

I'm not hearing Voiceover read that something has been sent, but they're definitely going through.

By Brian Giles on Saturday, September 23, 2023 - 13:36

Not working here. VO just makes the boundary reached sound when you can't flick any farther.

I tried unassigning the command in settings and setting it up again but still no luck.

By Frank on Saturday, September 23, 2023 - 13:36

Very odd!
So when I first discovered this command was not working, I reset voiceover to defaults. I lost all my keyboard shortcuts and others for Braile.
That was two days ago.

Just a bit ago, I figured what the hey I will reset all voiceover commands again. After that I switched voiceover off and back on.
And voila!
Three finger flick up in Braille screen input is now fixed and working.

Just the same what a truly unnecessary experience given this is an upgrade to make things better.

BTW you can find the reset commands under the Commands section of Voiceover and towards the very bottom of the screen.

Hope it works for you.

By Brian Giles on Saturday, September 23, 2023 - 13:36

Didn't work for me. Interesting idea though.

By Frank on Saturday, September 23, 2023 - 13:36

It worked just fine until my phone locked.
When I unlocked it after a while of being inactive it stopped working.
This is really wacky!

By Magic Retina on Saturday, September 23, 2023 - 13:36

I’m not sure if this will be what you need but I changed three finger swipe right to quick action and use that to send messages in most apps successfully. I use one finger swipe down for return and that also helps.

By Frank on Saturday, September 23, 2023 - 13:36

Thank you.
I did try something similar and it did not work.
Just got the boundery sound.

My original solution still holds, but with a weird twist.
After my last post, it started working again.
I have no idea what is causing things to work or not to work.
Frustrating as one has to be set to turn the rotor and find send.
I think I will call this one a transitory bug.
Starting to wonder if it is a screen bug.

By Frank on Monday, October 23, 2023 - 13:36

After putting our notes together and comparing heads with somebody else having the same issue we came up with the following conclusion.
If you got external keyboards paired or Braille displays which use a regular keyboard, and quick nav is on; the 3 finger flick up gesture will not work.
Just the same, if quick nav is on, it will not work regardless at this time whether you have an external device. Somehow it might have been switched on during upgrade etc.

Working solution at this time:

Assign a gesture to toggle quick nav on or off.
under all commands and voice over.
Utilize this gesture to switch quick nav off.
It should make a little fluity ascending noise when on, and the opposit when off.

Again, if you do not have external keyboards or Braille displays, this should not matter in theory.
But for now it looks like this is the case.

My other hypothesis is that the bluetooth connection may also be interfering, but that is still being tested with my headset, and no conclusions have been reached.

The above quick nav mentioned issue seems to be the culprit at this current time.