Not on my iPhone 6s Plus
[doublepost=1555967641][/doublepost]
Works fine with search engine: DuckDuckGo, with search engine suggestions turned on as well as safari suggestions.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iOS 12.3 Beta 3 ― Bug Fixes, Changes, and Improvements
- Thread starter Banglazed
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Not on my iPhone 6s Plus
[doublepost=1555967641][/doublepost]
Works fine with search engine: DuckDuckGo, with search engine suggestions turned on as well as safari suggestions.
Not sure. All I can do is smile when I look back at the first page at the two who claimed "e" and "f" builds were often more stable than "a" or "b" builds, and how they preferred them.
Rogers --> 36.0.1
[doublepost=1555968457][/doublepost]
Not getting this issue on XSM, Google is selected, search engine suggestions is on, same settings as always.
Intel iPhone XR/XS/Max: 1.05.01 to 1.05.02 and T-Mobile version 36.0.2
iPhone 6/6 Plus/SE: 7.61.00 to 7.70.01
iPhone 6/6 Plus/SE: 7.61.00 to 7.70.01
Did you report this to Apple? I haven’t seen anyone here say they did and Apple should be told (even though I suspect they read these threads!
)Did you report this to Apple? I haven’t seen anyone here say they did and Apple should be told (even though I suspect they read these threads!)
I submitted it.
I have two annoying problems in the iOS 12.2 final. Has someone experienced that in the beta too?
- Sometimes, when I’m opening an app, It doesn’t start. I only see a blank page. And the status bar is empty. No time, no battery icon etc.
- The keyboard is freezing very often. This also happens with third party keyboards
I have the XS Max.
- Sometimes, when I’m opening an app, It doesn’t start. I only see a blank page. And the status bar is empty. No time, no battery icon etc.
- The keyboard is freezing very often. This also happens with third party keyboards
I have the XS Max.
Except that doesn't really have a lot to do with it. More with how much code they change working on other items or new features or changes made is what requires more commits (a,b,c,d,etc). In later builds is when you see lower number of commits (a,b) typically because of code freeze. Doesn't really mean a build is bad or good relative to how many rev's there were of it though.Not sure. All I can do is smile when I look back at the first page at the two who claimed "e" and "f" builds were often more stable than "a" or "b" builds, and how they preferred them.
Is it just me or is the TV Provider setting missing in 12.3? It’s still present in tvOS but not iOS.
And guess what! Safari crashes on MacOS 10.14.5 beta 3...
with suggested search and google!
Downloading now and just noticed a bug on beta 2. WiFi is connected and active (as evidenced by the fact I was able to download beta 3) but my status bar does not reflect it.
Hoping it’s fixed in beta 3!
Hoping it’s fixed in beta 3!
I know it wasn’t in this build but when did they get rid of the “never” setting for autolock?
5 minutes is the longest it will let you do now.
5 minutes is the longest it will let you do now.
Sounds like you have a work email with restrictions. Mine did this when I added mine to the stock Apple Mail app.
iPhone X - Germany
Modem Version (is the same for me since 12.2 Final)
Carrier Version
Yes, the modem firmware is the same as 12.2 but previous beta 2 used an older firmware 2.03.05. It happens in beta testing that Apple will downgrade the firmware.
Updated all modem firmware on wiki
You are now able to adjust the aperture (Depth Effect) in real-time while in Portrait Mode. Tap the icon in the top right corner.
That's not what I understood the letters to mean. It was explained here in the forums that the letter at the end of the number signifies how many times it ran through internal QA before the build was released outside Apple.
And, historically, it's been my experience with iOS that the higher number of retries after a build has been made, the less polished it is as a result. A good example is the Safari bug we found earlier today. It wasn't there in Beta 2, which was a (d) build, but it showed up in this one.
This build had to go back once more through the QA cycle than Beta 2.
Last edited: