Same, all working again.I can access my work Outlook again so I’m guessing this was primarily a fix for the whole Office issue.
Is your whatsaap audio messages working as well? I can confirm Office 365 apps to be working, but I still have the issue on whatsappSame, all working again.
Looks like it's fixed the HTTP/3 issues too.I can access my work Outlook again so I’m guessing this was primarily a fix for the whole Office issue.
Is this with the new updated build?I can access my work Outlook again so I’m guessing this was primarily a fix for the whole Office issue.
Yeh seems like itIs this with the new updated build?
Yes, it’s true 👌It seems in this release that you can unlock your iPhone with Face ID wearing a mask *without* the need to be connected to WiFi, which seems to have been the case in the first release.
Can anyone else confirm?
I just go to Settings>FaceID and Passcode>[enter passcode]>scroll down to and slide the Unlock with Apple Watch slider to the right and its on. I don't even think you need to be wearing a mask for it to work. I think it just detects that it cannot open using FaceID and rolls over to unlock with the Watch. For me, its worked just like the Mac version.
I hate to revive this old trope, but this is a beta of a new feature and so it may not be working 100% correctly for everyone.
Still not working for me—requires wifi on Apple Watch (and, once wifi is enabled, it throws the "Unable to Connect to Apple Watch" error I was getting last time). Haven't had luck with this feature once.It seems in this release that you can unlock your iPhone with Face ID wearing a mask *without* the need to be connected to WiFi, which seems to have been the case in the first release.
Can anyone else confirm?
Why are you complaining about bugs in a beta release? Betas have bugs.Is this bug fixed yet? Seriously the bugs are getting more and more pathetic lately. White text on a white background......maybe if we just bought some upcoming Apple Glasses we could read again!
View attachment 1725065
Honestly, I have been reading this thread closely and I’m not surprised in the least they updated it. There seemed to be too many somewhat moderate issues that shouldn’t be present this far along into an iOS version. Ie Safari not working, apps not loading, cellular service cutting out, mail not working etc. It’s a bit nuts if you ask me. I actually predicted they wouldn’t release a public beta due to these issues, at least until beta 2. But it’s great to see they have nipped it in the bud this week. Hopefully public beta is to follow soon.Can someone explain this to me? We just got 14.5 beta 1 wtf is this? It’s not beta 2? It’s a security update to 14.5 B1?
I’m at a loss
Interestingly Safari with HTTP/3 enabled under Experimental Features works on my iPhone 12 but not on my iPad mini fifth-gen. Weird I know but the settings and configurations are otherwise identical—makes no sense to me. I've simply disabled it again on both devices.Also seems to have fixed the http/3 bug in safari. I turned it back on and it is working on the sites that were broken before.
Is the point of software testing and development not to point out bugs, flaws, and other things that should be fixed in order to push a more complete and usable final product? Or would you rather be immersed in an echo chamber of Apple bootlickers bent on retaining blind brand loyalty over actual progress?Why are you complaining about bugs in a beta release? Betas have bugs.
Still not working for me—requires wifi on Apple Watch (and, once wifi is enabled, it throws the "Unable to Connect to Apple Watch" error I was getting last time). Haven't had luck with this feature once.
No offense—I understand the approach because of the Watch's lack of U1—but this feature implementation in my experience thus far is unimpressive and clunky.
It’s incredibly less secure. Anyone with a mask can just point it at you as long as you wear the Watch even when you’re sleeping.Seems like if they detect a mask, they don't really scan for facial features (incl. attention)
It automatically switches to be authenticated with the Apple Watch.
So yea, slightly less secure for the sake of convenience.
Read his post again. It's one thing to ask if others are experiencing the same bug in a beta. It is quite another to complain as he did about the quality of Apple's software, because the beta has so many bugs.Interestingly Safari with HTTP/3 enabled under Experimental Features works on my iPhone 12 but not on my iPad mini fifth-gen. Weird I know but the settings and configurations are otherwise identical—makes no sense to me. I've simply disabled it again on both devices.
Is the point of software testing and development not to point out bugs, flaws, and other things that should be fixed in order to push a more complete and usable final product? Or would you rather be immersed in an echo chamber of Apple bootlickers bent on retaining blind brand loyalty over actual progress?
Because I'm not enabling and leaving on wifi—exposing myself to yet more electromagnetic radiation pollution and less importantly degrading the Watch's longevity—just to be able to use some half-assed feature like this one! 😄If I may ask, why does it bother you to have wifi enabled? You don't need to be connected to a network, it just needs to be enabled.
Because you're complaining about someone with valid criticism and observation. People like YOU are the problem <3Read his post again. It's one thing to ask if others are experiencing the same bug in a beta. It is quite another to complain as he did about the quality of Apple's software, because the beta has so many bugs.
Why didn't you address him? He is he one with the wrong expectations. I merely pointed it out.
Because I'm not enabling and leaving on wifi—exposing myself to yet more electromagnetic radiation pollution and less importantly degrading the Watch's longevity—just to be able to use some half-assed feature like this one!![]()