I just wanted to let everyone know that iOS 27.2 developer beta 3 is out. For those who installed it, what's your experience? Anything new? Any issues with it?
By Alicia Krage, 5 October, 2026
Forum
Apple Beta Releases
Share Your Bug Reports with AppleVis
If you experience a bug in Apple Beta Software, the most important thing you can do is to file a report in Feedback Assistant. Please do not assume that Apple is already aware of a bug or that your report won't make a difference; your report may provide crucial information, and submitting bug reports directly to Apple helps them reproduce and resolve the issue faster. The more reports they receive, the higher the priority Apple is likely to give to fixing the bug.
If you are using beta software, please use the Feedback Assistant on your device to submit feedback and bug reports. If you are using a public release, this blog post explains how to report the issue and what information to include.
In 2025, AppleVis launched the Community Bug Reporting Program with the goal of improving the quality and quantity of information we share with the community about bugs in Apple software releases. If you would like to contribute to this effort, please submit your reports via our Community Bug Report Form.
All reports shared with AppleVis must first be filed with Apple via Feedback Assistant. More information about the Community Bug Program is available here.
Comments
Apps on the home screen are behaving properly again
I just installed the beta and tested this with the BARD Mobile app. I locked and unlocked the phone several times and after swiping home, the app remained in focus each time.
Phone numbers are still not being read out in their entirety
Although there aren't many users on this forum who use the Simplified Chinese voice like I do, I still want to point out that a bug that has persisted for several versions remains unfixed in the beta released today. The specific issue is that VoiceOver fails to read phone numbers in their entirety. For example, if a number like "13812345678" calls you, what you hear on the screen is "Incoming call 1381234," and the last four digits, "5678," are not read out. There is another scenario that triggers this bug: when you initiate a call yourself. For instance, if you dial "13812345678," after you press the "Call" button, the screen displays "Calling 13812345678." However, if you use VoiceOver to read this text, it will only say "Calling 1381234," and again, the last four digits, "5678," are not read out.
one weird bug
I'm using an iPhone 18 pro with ios 27.2 beta 3. if you press and hold the power button, like, "call mom." it does it, but then it does it again.... and it's really weird. I will be reporting this to apple. otherwise, this beta seems relatively good.
Zach M
Check setting accessibility and Siri. They added typing beside press side button. Turn it off and on and do a restart. Good luck brave person.
Re: one weird bug
what do you mean it does it again?
explanation
so basically if I do the whole "call mom". it'll do calling mom. it makes the phone call. and then it'll go calling mom, again and does actually try to make the phone call multple times. it's kinda a mess. lol. what's even stranger, that only happens when doing phone calls, this does not happen when telling siri to do facetime audio. this was not an issue in 27.0.1 as that was the other version I worked with on this phone.
Not related to iOS, but
Has the App Store is in accessibility been fixed on macOS yet? Can you finally download apps normally?
VoiceOver behavior while connected to Bluetooth speakers
In iOs 27.2, Apple has breathed life back into the audio destination rotor item. Now, if you are connected to a Bluetooth speaker, even if you set the device type to a speaker in Bluetooth settings, VoiceOver will go through the speaker. But you can use the audio destination to direct the VoiceOver to the phone and music and other audio to the speaker. They introduced this several years ago. It worked for a while. then they broke it, and didn’t do anything about it. Let’s hope this time it will keep working. At least I like this implementation better.