Apple Screentime. 100 settings. If you crack the code it works. One wrong setting and the childs device is as open as a book.
Nobody on the Screentime team can actually use this product, because it's been totally bugged for a decade.
Bugs Apple loves
331–340 of 550 posts
Re: Bugs Apple loves
#332Another one I enjoy is the adventure of making a captive Wifi portal screen appear. Sometimes it will, sometimes it won't. Who knows why? Just reboot and try again.
Re: Bugs Apple loves
#333Earlier quoted context omitted.
Apple also makes it a biznatch to make a developer account separate from your personal account. In Apple's ideal world, multiple accounts should in no circumstance ever exist. I, in an ideal world, would agree with this. But we live in this world, where Apple bans accounts for redeeming legitimate gift cards.
And yet Apple CREATED the multiple-accounts problem for millions of people by implementing their idiotic "Apple ID must be an E-mail address" policy. So of course people thought that when they changed jobs, cable companies, or whatever... they needed to create a new Apple ID with their new E-mail address. This was reinforced when Apple further stupidified their policy by requiring your ID to be a WORKING E-mail addre…
Maybe in the 90's before Gmail came about so everyone still used their university or ISP email accounts.
Re: Bugs Apple loves
#334My 2022 M1 macbook sound input will slowly have the volume lowered to where no-one can hear me, regardless of what the device I'm using as a microphone. I run a permanent applescript that keeps the input volume at 80%, updated every 5 seconds. Apple doesn't care since it's a rare issue, never seen anyone else with this problem and I don't see how taking it to Apple Support will help.
Re: Bugs Apple loves
#335Earlier quoted context omitted.
It feels like Apple lacks the institutional vocabulary to even think about fixing old bugs. The way the releases are structured, there’s a “zero bugs” day where all bugs are ceremonially kicked out of the current release, and the level of quality is deemed to be “what we’re shipping with”. On that day, it’s not like the bugs are fixed, they’re just bulk-modified to target “future os release” and that’s that. Then the…
> But that’s ok because big rewrite of subsystem is gonna ship next release and it’ll probably make all the bugs invalid, right? Right? Well, it certainly won’t have more bugs, right? Right? They keep doing them, but I wonder to what degree these rewrites are necessary, and whether your average Apple engineer is aware that they end up with more bugs and vulnerabilities than they started. Surely they've gotta know?
People look at the backlog of issues, see all the things they don't like about $subsystem, and think to themselves "we ought to rewrite this". The incentives are all aligned to make this common. Project managers get a nice chunk of work to manage, engineers get to write things their way, managers get a nice thing to add to their accomplishments, everyone feels like progress is happening. Heck, sometimes there may actually be real deficiencies in the existing code that are being addressed! And in the end, the bug count is lower! (Never mind that it's only lower because it hasn't had the time in production to actually find the bugs yet...)
Large-scale software is hard. So hard nobody's really managed to do it well. By large-scale I don't mean "a lot of users" or "a large deployment"... I mean "a lot of engineers". Once the number of engineers gets large enough, they start making decisions that make the product worse, more bloated, more buggy, and no human is capable of keeping it in check, because the sheer amount of activity in the code is so large you can't possibly keep up with it. And the worst part is that orgs try to solve this by... hiring more engineers to wrangle the complexity. By this point you're already sunk, there's no going back.
Re: Bugs Apple loves
#336Earlier quoted context omitted.
The article lists very obvious functional regressions (that I use everyday), I would not have missed them.
I can't believe that anyone in the world has had Airdrop work for them perfectly, every time, every day. It has a less than 50% success rate with me, and that makes it sound better than it is.
It has worked for me every time, at least on iOS 18. It used to conk out when storage is low.
Re: Bugs Apple loves
#337Re: Bugs Apple loves
#338Earlier quoted context omitted.
> …since I switch between languages. You can easily switch between keyboard’s languages in the globe icon close to the spacebar.
Can't find it. I can see the keyboard layout per language but not actual languages. One layout is enough for all of my languages.
You need to enable more keyboards in System Settings -> General -> Keyboard -> Keyboards
Re: Bugs Apple loves
#339Earlier quoted context omitted.
And they had it solved! 3D Touch worked perfectly – you pushed the screen hard to get a cursor, moved it to the start of the selection, and pushed hard again to drag to the end. They killed it because "not all iPhones had the hardware to support it" or something.
You can still get a cursor by holding down space bar.
that deserves a whole separate opera. why does moving the cursor to start/end almost always place it one character off? same when trying to use touch on text for it.
Re: Bugs Apple loves
#340The macOS login screen is broken since basically forever. Opening a macbook lid and choosing another user than the one already selected is a PITA. I can't even remember it working. And I have the issue on 3 macbooks.
Press escape, select the other user, login?