The only iOS 13 bugs I’ve been bitten by are: 1. Safari’s back button now seems to lose the position on the previous page - sometimes. 2. The share sheet has a row of Messages contacts that I didn’t ask for, don’t want, and can’t turn off - and it creates the risk of super-inappropriate sharing, because all my work contacts are eligible for being on this row, seemingly at random.
I’ve encountered so many iOS bugs (both in 13 and previous versions) I’ve strongly considered making a website documenting them all. I honestly think Apple CarPlay is the buggiest thing I’ve ever used.
Why iOS 13 and Catalina Are So Buggy
291–300 of 368 posts
Re: Why iOS 13 and Catalina Are So Buggy
#292Earlier quoted context omitted.
Win 10 is fine for me.
Windows 10 is fine for me too, altho UWP apps seem really laggy. I understand the logic of callback style coding, but it seems like you click a button, and then the system graciously responds. Whereas in non-callback style coding, the system begins to do something and you feel like it's definitely on the job. It would be nice to have some kind of feedback constantly linking the button press to the response that happe…
Re: Why iOS 13 and Catalina Are So Buggy
#293Yesterday a coworker was frustrated with his computers, and said something insightful: "When software gets past a certain age it just gets bad." He was referring primarily to Android and Windows (10) but it applies to every piece of software that suffers from feature creep. If it's a cash cow they have to keep stuffing new things in and periodically repainting it to make it look new again. Around 10.9, MacOS reached…
I'm reading this on a late-2013 MBP retina running 10.9.5 and not only does it do everything I need it to do, "upgrading" from here would actually cause me to lose essential functionality (which is why I haven't done it). I have a stash of replacement MBPs to replace this one with when it finally does die, but I don't know what I'm going to do when they're all gone because AFAICT everything Apple is producing nowaday…
You make it sound like they're t-shirts or something haha
Re: Why iOS 13 and Catalina Are So Buggy
#294Re: Why iOS 13 and Catalina Are So Buggy
#295Yesterday a coworker was frustrated with his computers, and said something insightful: "When software gets past a certain age it just gets bad." He was referring primarily to Android and Windows (10) but it applies to every piece of software that suffers from feature creep. If it's a cash cow they have to keep stuffing new things in and periodically repainting it to make it look new again. Around 10.9, MacOS reached…
Re: Why iOS 13 and Catalina Are So Buggy
#296Earlier quoted context omitted.
I'm reading this on a late-2013 MBP retina running 10.9.5 and not only does it do everything I need it to do, "upgrading" from here would actually cause me to lose essential functionality (which is why I haven't done it). I have a stash of replacement MBPs to replace this one with when it finally does die, but I don't know what I'm going to do when they're all gone because AFAICT everything Apple is producing nowaday…
> I have a stash of replacement MBPs You make it sound like they're t-shirts or something haha
Re: Why iOS 13 and Catalina Are So Buggy
#297Yesterday a coworker was frustrated with his computers, and said something insightful: "When software gets past a certain age it just gets bad." He was referring primarily to Android and Windows (10) but it applies to every piece of software that suffers from feature creep. If it's a cash cow they have to keep stuffing new things in and periodically repainting it to make it look new again. Around 10.9, MacOS reached…
Re: Why iOS 13 and Catalina Are So Buggy
#298Re: Why iOS 13 and Catalina Are So Buggy
#299But is each release actually worse than the last?
My guess is, not really, though the perception persists for a couple main reasons:
(1) For a certain subset of people, the last release really was worse than ever before. New releases have new bugs, and those bugs will affect a certain subset of people that isn't necessarily the same as the bug from the last release. Those people complain (justifiably, I think) though of course people don't create a lot of posts to describe the problems they aren't having.
(2) We all naturally forget about the annoyances of years past while focusing on the current annoyances. (Generally, that is.)
Re: Why iOS 13 and Catalina Are So Buggy
#300That doesn't make sense. None of this has changed from previous updates and all previous macOS updates were far more stable than this one. This isn't a particularly feature laden update either. But now all of a sudden we get catastrophic (deleted emails) and less catastrophic (missing Music playlists) data loss, crash bugs and generally weird behaviour of many apps. I have identified one particular area where bugs ar…
My car isn't new (2007) and lacks the built in bluetooth-ish stuff. So I have my iPhone connected to the aux via the lightning-to-headphone jack adapter. My Apple Watch is my means of adjusting music: not perfect, but I have a rule (seems to be the bare minimum) that I only track forward/back/whatever if I'm on the interstate and there are no cars near me even though the hand with the watch on it is on the steering wheel (I'm glancing, so that's a cautionary thing that even though it is brief, I could be a danger to others). Well, since the latest updates and point releases we're now at the stage where the Apple Watch has a hard time staying in sync with my iPhone. If I start a track, the watch is aware and the now playing "app" is visible. But if I pause the song and the Watch blacks out, if I activate it, I'm back at the main watch face with time and date. Before, it'd return to playing now and I could tap play button and be good to go. Instead, I need to wait until I'm at a stop and turn it back on via the iPhone (in which case, watch now shows now playing again) or hope "Hey Siri, resume music" works.
This also falls into what the article talks about that it is a regression in behavior that doesn't, seemingly anyway, involve a crash. It's terrible, but it isn't going to register on any of their logs/reports because the devices seem to be functional throughout.