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

121–130 of 368 posts

Re: Why iOS 13 and Catalina Are So Buggy

#121

Post by dwaite »

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

Apple operating systems are on a semantic versioning system with regards to API. The idea is that API only break on the major version update which is released each year (ignoring that a the OS X version has a "10" in front of it).

Non-breaking API additions and userspace features which do not impact API can be rolled out throughout the year though. There are also changes to private API throughout the year since the Apple apps using them are distributed with that operating system release.

Generally, API grow up as private API that get adopted by other Apple apps, then may get promoted to public once they are stable and maintainable.

IMHO, the big issue with iOS 13 and Catalina this year was that there were several huge developer features and internal system refactoring which were maturing during beta. This slows down everyone who is dependent upon those features. The solution there is to require public API to have a higher level of maturity before that beta 1 release.

I disagree that Apple is waterfall, because their release dates are fixed, and they will change what will be delivered to make that date. I don't know if a twice annual major feature releases (and corresponding WWDC summer and WWDC winter) fixes anything, or if it just makes the life of third party developers harder.

Re: Why iOS 13 and Catalina Are So Buggy

#122

Post by mrweasel »

greggman2 wrote: post #65

tvOS 13 seems to also be buggy. After the update I can no longer wake it via HDMI/CEC. Once I wake it some other (inconvenient) way then HDMI/CEC control works. Wake up was working on tvOS 12

I had to disable HDMI/CEC a while back because the AppleTV kept switch the TV back to it's own HDMI, stealing "focus" from the PlayStation.

Re: Why iOS 13 and Catalina Are So Buggy

#123

Post by cmroanirgo »

NobodyNada wrote: post #62
tobr wrote: 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).

I have Safari 13 on High Sierra

Re: Why iOS 13 and Catalina Are So Buggy

#124

Post by ljsocal »

justinv wrote: post #21
aloknnikhil wrote: post #16

I am also finding text selection in iOS 13 hit/miss. I either cannot activate the text selection or I cannot select without the cursor jumping all over the place. Also, I miss the magnifying glass for text selection. Did Apple remove that?

Hold down the space key as if you would be force touching it. It will make your finger become the "cursor". Slide it around as you see fit.

Brilliant, thanks for this!

Re: Why iOS 13 and Catalina Are So Buggy

#125

Post by 333c »

torben-friis wrote: post #111
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 have one where notifications aren't clickable (tappable?) on the lock screen, and I need to turn the screen on and off several times for them to work or just go to the app manually. Strangely enough they can be dismissed through swiping, the click event registers but just does nothing.

Interesting. I seem to have the opposite: some notifications I can't swipe right (finger moves left to right) to open, but I can tap on them to open them.

Re: Why iOS 13 and Catalina Are So Buggy

#126

Post by mistahenry »

fingerlocks wrote: post #99
Svoka wrote: post #45

Earlier quoted context omitted.

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…

Lol this one was painful. And they also moved where the peripheral identifier is located in the object hierarchy to a superclass CBPeer which was wrapped in available MacOS 13+. So all my existing code that referenced the identifier on the CBPeripheral where it was prior to MacOS 13 needed warning suppression since identifier has been available through the object hierarchy on peripheral since forever

Re: Why iOS 13 and Catalina Are So Buggy

#128

Post by yankcrime »

alwillis wrote: post #36
threeseed wrote: post #19

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.

Every .0 release for iOS and OSX has been buggy. Every single one. I've run and tested every release going back to 2001 and it's been a while since a macOS release has been this buggy and caused serious data loss in some cases. So even for .0 release, this has been pretty bad.

There was the data-loss bug that plagued the Snow Leopard release.

Re: Why iOS 13 and Catalina Are So Buggy

#129

Post by TheOtherHobbes »

saagarjha wrote: post #117
Someone wrote: post #106

Earlier quoted context omitted.

”It makes very little sense for a resource constrained company to rewrite stuff” I don’t think ”for a resource constrained company” makes a difference there. That’s good, because I have a hard time thinking of Apple as resource constrained.

Apple doesn't actually have a lot of engineers on most projects.

The resources are there to hire engineers. If they're not being used to hire engineers that's a management choice, not a resource constraint.

Re: Why iOS 13 and Catalina Are So Buggy

#130

Post by saagarjha »

TheOtherHobbes wrote: post #129
saagarjha wrote: post #117

Earlier quoted context omitted.

Apple doesn't actually have a lot of engineers on most projects.

The resources are there to hire engineers. If they're not being used to hire engineers that's a management choice, not a resource constraint.

It's certainly a management choice. I don't think Apple would be better served by just going out and hiring more engineers.
Post reply on HN