Live data from Hacker News

Why iOS 13 and Catalina Are So Buggy

tidbits.com

91–100 of 368 posts

Re: Why iOS 13 and Catalina Are So Buggy

#91

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

> For example, when I upgraded from Mojave to Catalina, an 'Moved Files' directory appeared that contained some files (that was once) in /usr/local/

This is a consequence of the read-only root filesystem in Catalina: https://support.apple.com/en-us/HT210650

Even with SIP disabled you can't do shit to that volume until you remount rw (at least, this was reported to work in betas, haven't seen anyone test the shipped OS).

Re: Why iOS 13 and Catalina Are So Buggy

#92

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

Cf with Microsoft I think they are ok. Past mart just cannot upgrade. Now is so much I have to take a rest and avoid the upgrade.

Re: Why iOS 13 and Catalina Are So Buggy

#93

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

> For example, when I upgraded from Mojave to Catalina, an 'Moved Files' directory appeared that contained some files (that was once) in /usr/local/ This is a consequence of the read-only root filesystem in Catalina: https://support.apple.com/en-us/HT210650 Even with SIP disabled you can't do shit to that volume until you remount rw (at least, this was reported to work in betas, haven't seen anyone test the shipped O…

> This is a consequence of the read-only root filesystem in Catalina: https://support.apple.com/en-us/HT210650

Actually, that's not the case, b.c. /usr/local/ isn't included in the read-only file system.

Re: Why iOS 13 and Catalina Are So Buggy

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

[deleted]

Re: Why iOS 13 and Catalina Are So Buggy

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

Bug 1 is driving me nuts but found it hard to confirm that it was affecting others or was even new. Strangely, I feel slightly better now!

Re: Why iOS 13 and Catalina Are So Buggy

#96
post #56

Earlier quoted context omitted.

Very little has been rewritten in Swift.

Really? I read otherwise: https://blog.timac.org/2019/0926-state-of-swift-ios13/ It'd be hard to know unless you worked there. It's just a wild theory, I might be wrong :)

It makes very little sense for a resource constrained company to rewrite stuff that just works in Swift especially when it has a lot of low-level code. What they do sometimes is adding a Swift-friendly API layer around the Objective-C(++) code. Newer libraries that are not too low-level oriented might get written in Swift nowadays.

Re: Why iOS 13 and Catalina Are So Buggy

#97
iOS 13 was pretty buggy but the amount of improvements all across the system has been significant. I can live with it. But installing Catalina on my daily driver: no thanks. Xcode will force me to upgrade eventually I guess.

Re: Why iOS 13 and Catalina Are So Buggy

#98
post #44

I'm still on High Sierra on my 2015 Macbook Pro. I haven't upgraded my OS nor my machine and pretty happy with it (I only accept updates within my OS version itself) . On my home machine, I do use Mojave, which by itself is quite buggy and I'm waiting for some more fixes before I upgrade my Macbook Pro to Mojave as well. I never install Apple's newer OS'es because I have a lot of development related stuff setup on my…

The "Regressions Get Fixed. Old Bugs Get Ignored." thought does not help your strategy.

After 6 months into the new version of iOS and MacOS, there is a lot less attention to fix problem in the previous version of the OS. It is even worse when it comes to firmware problems on older hardware.

If you have a 2+ year old Apple device you need to hope that all the security bugs on your hardware are also in the latest software or hardware, otherwise it may just never be fixed.

Re: Why iOS 13 and Catalina Are So Buggy

#99
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…

> I can’t even name single such change for iOS.

I can give you one. A few years back an important interface was arbitrarily renamed in the CoreBluetooth stack. I would look it up, but I’m on mobile and laying in bed. Ask tomorrow and I’ll find it.

anyway, I was overseeing a half-dozen BT apps for a hardware company at the time. Was a real pain to go through all those projects and #ifdef the interface name for the iOS version. Very odd change since I’ve never seen Apple do anything like that before either.

Re: Why iOS 13 and Catalina Are So Buggy

#100

Every .0 release for iOS and OSX has been buggy. Every single one. And then a few point releases later and it's all forgotten. And then the next .0 release arrives and the blog posts reappear.

My very first Mac was the PowerBook G4, and I waited over a month to buy it even though there was a game I wanted to play because they hadn’t hit the 0.2 release of the OS.

It amazes and frustrates me to see people get all shocked about when I already knew this about Apple even before I was a customer. Fifteen years ago.

Nothing. Has. Changed.

Nothing.

At some point you need to blame yourself for being taken in again. It’s “fool me twice”, not “fool me eight times”

Post reply on HN