Live data from Hacker News

Why iOS 13 and Catalina Are So Buggy

tidbits.com

71–80 of 368 posts

Re: Why iOS 13 and Catalina Are So Buggy

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

Re: Why iOS 13 and Catalina Are So Buggy

#72
post #6

Are they that buggy? They seem very stable to me and I’ve been running them since the betas.

I'm on the second-latest MacBook Pro. I completely erased my disk and installed a fresh copy of Catalina when it was released. It's been patched with the post-release update. Almost all settings are at their recommended defaults, there is no third-party stuff that modifies system behavior, and I mostly only use Apple's own apps and services for stuff like music, books, cloud, mail etc. And boy yes there are bugs. Not…

The public beta, code named Kodiak was awful. As were, 10.0 (Cheetah), 10.1 (Puma), 10.2 (Jaguar) and 10.3 (Panther). 10.4 (Tiger) was initially terrible, but did improve massively. 10.5 (Lion) was comparatively awful and quite jarring with it’s nit insignificant UI overhaul...

The point I’m making is that there is an awful lot of looking back with rose tinted glasses going on. It happens every time there is a new release. Thing is, every OS seems to suffer this, not just Apple.

Re: Why iOS 13 and Catalina Are So Buggy

#74

Earlier quoted context omitted.

This seems like a really good idea to me. Is it possible to do in a way that preserves privacy and doesn’t basically become a hidden “telemetry” system?

Make it opt-in and require a privacy review every time something like this goes in?

If you make it opt-in, the company will not get a lot of reports. If you want to get enough data, they should be opt-out as the others.

Re: Why iOS 13 and Catalina Are So Buggy

#75
I've having a feeling that iOS 13 & Catalina is felt buggy b.c. it's not the operating system itself that's buggy but that the updater is buggy. Many things have changed in this release, and the installer/updater had to handle too many different scenarios.

For example, when I upgraded from Mojave to Catalina, an 'Moved Files' directory appeared that contained some files (that was once) in /usr/local/. I don't remember such directory appearing after an macOS update, and I've had many friends (that aren't really technical) appear that to them. There were lots of new applications (like Music.app and Podcasts.app), and data migration between internal databases weren't perfect.

I've installed Catalina two times, first by upgrading from Mojave and second a clean re-install. When I upgraded Mojave, I found too many bugs that I was worrying about data-loss, which lead to a full backup (I do backups regularly) and a clean re-install. (Admittedly, this was my first clean reinstall for a major macOS update) I clean-installed Catalina and manually restored all of my files from the backup, and except for some minor bugs I'm good.

It's a pity that updates aren't seamless, but if there's anyone having trouble with various Catalina bugs, (while Apple updates it's imperfect macOS updater) I would recommend a full clean re-install for macOS Catalina.

Re: Why iOS 13 and Catalina Are So Buggy

#76
post #45
post #32

After doing some iOS/Mac development, I'd say some bugginiess is caused by changing APIs and behaviors inflicted by Apple, expected to be absorbed/dealt with by developers. They mercilessly do this with every release and no doubt that affects their internal projects. Also, xcode has gone the way of iTunes and ObjC was always a huge pain. It's a really hostile environment to develop in, where you're having to play cat…

Wow. My experience is opposite. Been in iOS development for over 10 years already, little less for Android. App made for iOS still works with very minor adjustments, while on Android it’s a mess. We was forced to change build system several times, breaking changes and just silly API renames, service depreciations, generations of push services, forcing firebase and AndroidX, change of permission model, of concurrency…

Unfortunately, just because the developer experience on Android can be even worse, that doesn't mean the developer experience on iOS isn't bad.

Re: Why iOS 13 and Catalina Are So Buggy

#77
post #24

As a VoiceOver user, I can provide a lesser known perspective. I've gotten used to waiting several months until I actually install a new major release. With the exception of iOS 12, basically all releases since iOS 5 were quite buggy when it comes to apples screen reader VoiceOver. Luckily, applevis.com these days publishes a list of known problems with accessibility on iOS a few days before every major release. So t…

> their accessibility stack is still lightyears before Android. Don't you mean "ahead of"?

Yes, "ahead of" probably sounds better. I am not a native speaker.

Re: Why iOS 13 and Catalina Are So Buggy

#78
post #55

Tangentially related: GitHub has already dropped support for Mojave. The whole site is now broken in Safari 12 because it’s no longer the “current” version of the browser. Well, it is if you run Mojave, as you need to upgrade the entire system to get Safari 13. I can understand not developing new features for Safari 12, but speaking of regressions, why would you go break things that used to work a week ago?

Safari 13 is supported on Mojave. You can install it in System Preferences->Software Updates (there's a link that says "more updates" or "other updates" or something along those lines).

Thanks you, I did not know this. I looked into it a few days ago and Apple’s support page[1] seemed to tell me pretty clearly that I had to upgrade. I know see the small print that says:

> For some earlier versions of macOS, Safari might also be available separately from the Updates tab of the App Store.

1: https://support.apple.com/en-us/HT204416

Re: Why iOS 13 and Catalina Are So Buggy

#79
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 completely agree with point 2, and I have already accidentally shared a hacker news story to a work colleague without intending to!

I can’t understand why there is no option to remove it.

Re: Why iOS 13 and Catalina Are So Buggy

#80
post #63

> apart from a few specific areas, Apple doesn’t do a lot of automated testing. Apple is highly reliant on manual testing, probably too much so. That's the last thing I expected to know about such a big company.

When I interviewed at Apple last year, they emphasized their use of various robotic contraptions for end-to-end testing over unit tests. One engineer remarked that 20% test coverage was considered on the high end for his team.
Post reply on HN