Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
You're reminding of when people created problems for IT staff, they always walk up to you on a Friday afternoon and complain about something.
Yeah, they complain about something that happened 3 days ago, but can’t replicate now, but I’ve got this OTHER problem now ….
 
  • Like
Reactions: StyxMaker
The revised version also changes how the flashlight works. Instead of an instant light it quickly fades in and when turning It off it fades out.
 
  • Like
Reactions: mblm85
The revised version also changes how the flashlight works. Instead of an instant light it quickly fades in and when turning It off it fades out.
I believe that’s how it was in previous betas too. I just tried it on the old beta 4, it doesn’t fade in when turning it on. Glad to know its fixed with the revised build.
 
  • Like
Reactions: summiter
I have to install now to see if microphone bug has disappeared.
Actually the betas may not fix it as it’s something in the settings that prevents it. The way to stop the Microphone bug is to ‘Reset All Settings’ via the settings app
 
Meanwhile, no Public Beta updates this week for iOS or iPadOS, despite new tvOS and watchOS releases.
The Public Beta update is typically released the day after the Dev Beta, once it is confirmed to be somewhat stable. As they just released a second version of Dev Beta 4 on Friday, there was probably something wrong with the release. Look for Public Beta 2 to be released on Monday the 29th or Tuesday the 30th.
 
  • Like
Reactions: gank41
Slightly newer build -- 22A5316k (new beta 4) vs 22A5316j (old beta 4), where the letter postfix supposedly indicates stability (a = most stable, z = least stable).
That is not at all what this letter means. It means how many runs through QA a build had. You could argue that the higher the letter, the more bugs they found and fixed before release.
 
  • Love
Reactions: addamas and gank41
Actually the betas may not fix it as it’s something in the settings that prevents it. The way to stop the Microphone bug is to ‘Reset All Settings’ via the settings app
AccessibilityUIServer is accessing microphone all the time. It appears once I start tethering. When I restart the phone, it disappears but once I start using tethering, it stays even after I end tethering.
I have reset all settings now. Looks like it's worked. Thanks!
 
  • Like
Reactions: AsarTheGod
Also doesn’t fix the emoji picker not learning the recently used ones or the modem crashes causing loss of signal momentarily. I’m not sure how this can be a public beta with those glaring bugs tbh, but I bet it ends up being released as public beta 2.
 
Battery life on this beta and especially the watch remain horrid. Restored to a fresh device and same issue. Watch isn’t even worth wearing now as it does in 4 hours. Apple beta quality has gotten so bad now I’m about to just be done. Their engineers really are all over the place. The “stable” 17.5.1 lasted longer but new iPad pros reboot randomly still. Just don’t find the polish with Apple as we used to. Very disappointed in what Tim Cook allows to happen now from a standards perspective.
 
Battery life on this beta and especially the watch remain horrid. Restored to a fresh device and same issue. Watch isn’t even worth wearing now as it does in 4 hours. Apple beta quality has gotten so bad now I’m about to just be done. Their engineers really are all over the place. The “stable” 17.5.1 lasted longer but new iPad pros reboot randomly still. Just don’t find the polish with Apple as we used to. Very disappointed in what Tim Cook allows to happen now from a standards perspective.
Any battery optimization won’t be seen until the final betas or maybe even the RC. No one should be expecting a beta to have ok battery life.
 
where the letter postfix supposedly indicates stability (a = most stable, z = least stable).
That is simply wrong.

The letter at the end of the build indicated the number of compiles, that one specific build went throu.

So at some point, one specific build is assigned as a „to be released“ beta version.
So the first compile of that specific build (let’s say 22A5316) is done —> a
Second compile of a specific build then would be —> b, and so on.

After each compile, there is some quality testing done and if those tests are not passed, another compile of that specific build has to be done.

So a higher „letter“ at the end actually only indicates one build went throu more quality checks for the milestone, they wanted to reach (beta 4 for example).
 
Becuase if it breaks somethig you are working over the weekend.

Edit: My last company the sytem auto rejected pull request on Friday afternoon.
Oh no, you mean people have to work a weekend day, as if that's not the world we live in now. :rolleyes:
 
Nope

Same old story

Signal cuts out then restores itself

Well


At least it’s coming back up innit

I should be glad it’s not dead altogether 🤣😂😂🤣
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.