Hi folks, I’m still using iOS 18.4.1, haven't updated to iOS 18.5 yet since some people said there’s a new bug in iOS 18.5. After using the quick action command on the Braille Screen Input with a three-finger swipe up—like for sending messages—the keyboard hides itself and you have to reactivate it again. Is that true? If so, it’s pretty problematic, since I often send messages one after another.
Also, in iOS 18.4 or 18.4.1 (not sure which one), a new bug was introduced. When viewing notifications—especially if you have a lot—VoiceOver can’t see all of them at once, and you have to keep doing the three-finger scroll, which is super annoying. Do you guys also have this issue in iOS 18.5? Thanks!
Comments
My experience
With regards to BSI while sending messages. I can type out a message, do a three finger swipe up to send it, type more messages, rents and repeat. This is in the messages app. I am running iOS 18.5 on an iPhone SE 2022.
I, Will, say that it is very beneficial to disable "Raise to Speak" in the Messages settings, so that when you are trying to perform BSI, you do not accidentally activate the microphone feature that lets you record a voice message from within the Messages app, by covering the proximity sensor near the earpiece.
Regarding notifications, I do have to scroll if I have a lot of notifications, however I am using list view, and I have a smaller device than most of you all, so yes for your second question.
HTH. :-)
Keyboard buck
Yes. When sending messages by using the 3-finger swipe Via BSI, the keyboard gets hidden in IOS18.5. The best and quickest way to unhide the keyboard is to try and power down your phone, but before it shuts down you need to re-enter your password.
Oh...
So, Brian doesn't have the issue while sechaba does... Don't know whether to switch or not.
To power down my phone...
Is it a joke I really didn't understand or what? I just don't wanna deal with a new bug hahaha
I don't understand the other response either
I am wondering if it's perhaps newer model iPhones that have this bug? Or if it's only in certain applications? As I mentioned, I tested this with the default messages app that comes with iOS, and do not have any issues. I don't use WhatsApp, and I don't do social media, so I am limited on how and where I can test this.
Again, I have not experienced the issue with the BSI going away, or having to reboot my phone to get it back or anything like that.
For transparency sake, I do not have any BSI controls in the rotor, I instead use the edge of screen touch Cheshire to activate BSI. I also do not have BSI set to automatically launch the keyboard when I enter a text field.
Finally I do have the box checked to keep BSI and command mode after opening an application.
HTH.
I am not experiencing this problem.
I have a 16 pro which is about as new as you can get, other than the 16E, and I can send messages with no problems whatsoever.
@Jo Billard
Well, I use an iPhone 15 pro max; so if you don't have an issue; I don't think that I will. Thank you all guys!
@brian
Bsi itself does not disappear. However, the keyboard certainly disappears after using the 3-finger swipe gesture to type. Since you don't use whatsapp, for instance, you probably won't experience this.
What happens, for example, since when searching for items on whatsapp you can't type using BSI, once your keyboard has disappeared you won't be able to use the standard querty keyboard to type. The same thing happens on my banking app, where you have to type authentication numbers to login. BSI is unusable on this app, and you have to type using querty keyboard. By the way I'm using iphone 15ProMax.
Maybe my explanation on this matter is not as clear as I would like it to be, but pardon my poor English on that one.
@mert oza
If you interact with apps which allows you to type using BSI, then you don't need to worry about the hidden keyboard. The problem arises where the app does not allow you to type using BSI. If your keyboard is hidden, in which case voice over will announce, then you may have to try powering down your phone!
@sechaba
Ah, thank you for the explanation.