Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why iOS 13 and Catalina Are So Buggy

tidbits.com

Post reply on HN
Print view View original

251–260 of 368 posts

Re: Why iOS 13 and Catalina Are So Buggy

#251

Post by city41 »

jl6 wrote: post #71

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.

Re: Why iOS 13 and Catalina Are So Buggy

#252

Post by squiggleblaz »

PaulHoule wrote: post #212
acollins1331 wrote: post #179

Earlier quoted context omitted.

This seems pretty far removed from most other people's experiences.

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 happens.

Re: Why iOS 13 and Catalina Are So Buggy

#253

Post by mason55 »

steve19 wrote: post #85
ChrisCinelli wrote: post #67

I did not work for Apple but this article describes exactly what I was thinking. Apple has very waterfall cycle. Everything is planned year after year to be released for the September event. When the deadline approach teams realized that are behind and they need to overwork. And when people get tired and under pressure, they usually introduce even more bugs. The article also nails the solution: a more Agile workflow.…

They could simply decouple the apps from the OS, like Android. Safari and Mail.app do not need to be tied to OS releases. Android OS releases do not get nearly as much fanfare because a lot of core functionality is decoupled from the OS: app store(s), mail clients, browsers, todo lists, even the text messaging apps and some security frameworks. Which of course is exactly why Apple keeps everything in one big release.…

I wonder if there's some anti-trust consideration to it. If Apple were able to update all their apps separately from the OS that would mean they had accessible APIs to do it. People would complain a lot more loudly about Apple blocking replacement functionality and Apple wouldn't want to allow a replacement for, eg, the messages app.

If you integrate the apps directly into the OS then you can just say that no APIs exist, those are just features of the operating system itself.

Re: Why iOS 13 and Catalina Are So Buggy

#254

Post by elagost »

ianlevesque wrote: post #249
elagost wrote: post #243

Yesterday 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…

> Running older Android versions reminds me of how fast and slick they were Those are some rose-tinted glasses for sure. Android lacked basic performance and stability for years after release.

I apologize for not being clear; I was referring primarily to 4.4 "KitKat". Still have a tablet that I run with that on it (offline) to read ebooks. Quite nice. You are correct though - pre-4.0 was pretty rough.

Re: Why iOS 13 and Catalina Are So Buggy

#256

Post by m3kw9 »

m3kw9 wrote: post #255

The bugs shows very increased complexity in the system, which causes so many exceptional scenarios that it is hard for QA to catch them all. This is the reason

They need one year of tech debt payback to get things back on track like what happened to one of their prev releases.

Re: Why iOS 13 and Catalina Are So Buggy

#257

Post by squiggleblaz »

huffmsa wrote: post #181
huffmsa wrote: post #180

Earlier quoted context omitted.

That's quickly becoming the main point of differentiation in most reviews since cars in a certain class have become more or less the same performance wise. Speaking from the perspective of just wrapping up the car buying process. All of the reviews had just as many, if not more words devoted to the infotainment experience as to the driving experience. Here I am thinking Bluetooth is peak feature so I can play my musi…

But as I've been saying for a few years now, most people don't want to drive . They'd much rather be driven so they can mess with their phones.

I want to drive. Just not to work (or the shops, or anywhere else on a daily basis).

Re: Why iOS 13 and Catalina Are So Buggy

#258

Post by mikestew »

makecheck wrote: post #246
jl6 wrote: post #71

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 believe the contacts list you’re referring to is generated by AirDrop based on nearby contacts. You can’t reorder it or edit the list but you can turn it off using Settings for AirDrop.

I believe the contacts list you’re referring to is generated by AirDrop based on nearby contacts

The 12 year old girl across the street who helps me walk our dogs on a regular basis (hence why she's in that bar), whose father works for Google, and has an Android phone is most certainly not showing up due to AirDrop when I'm in my living room.

And I'm with parent comment: I DO NOT WANT 12 year old girls to be one accidental button push away from inappropriate content. Hell, I don't want to explain to my bluegrass pickin' buddies why I sent them an Ikea link, either.

Re: Why iOS 13 and Catalina Are So Buggy

#259

Post by selectodude »

campfireveteran wrote: post #48

I refuse to install iOS 13.0 because it's so buggy, and refuse to install Catalina because all it does is take away features rather than adding value. They can't seem to stop to fix what's already broken, so they add a few things, break a few more and remove some I use and say "the emperor's new clothes are awesome."

13.1 is out now, and it's pretty slick.

Re: Why iOS 13 and Catalina Are So Buggy

#260

Post by alphakappa »

hobs wrote: post #202
jwr wrote: post #104

I have a slightly different take on this. I think every company should dedicate a certain percentage of their revenue to handling bug reports from users. Yes, many bug reports will be bogus, but many will be pure gold (I speak from experience). Yes, it involves a lot of manual work. But it is so incredibly worth it — you get to catch the odd bugs that you will never catch with automated or in-house testing. In contra…

Just a not that there is a way to get a bug report filed - call support, get the issue escalated because its not fixed, if they cant fix it it will go to engineering. I have personally witnessed hundreds of support cases go through this various process, in some cases taking months of work (for communication mostly from eng to customer) of T2 support reps. Now - is their current spend sufficient? Probably not, but App…

While this is true, it is a solution for people dedicated to getting a problem fixed. Calling up a support line is a huge barrier, and companies lose out when people cannot file bugs or express their frustration with little issues with ease.
Post reply on HN