Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
This could and would still happen even if none of those things that you mentioned happened and even if everything you mentioned was in place and running.

Would it happen more or less frequently after a feature freeze and a top/down review of the code base for a year?
 
  • Like
Reactions: dysamoria
I'm just wondering what triggered it for me, since I hadn't used the booking.com app for weeks when this bug spontaneously reared its ugly head.
 
  • Like
Reactions: Benjamin Frost
I'm just wondering what triggered it for me, since I hadn't used the booking.com app for weeks when this bug spontaneously reared its ugly head.

I don't believe you had to even use the Booking.com app to experience the issue. Simply having it installed was enough to set the proper stage for the issue to be triggered. I had the app installed, but had yet to use it, and I started experiencing the issue on Sunday, March 27th. It's been a slightly annoying 4 days for me, but nothing I couldn't handle.

For lack of a better understanding of the technical nitty-gritty, their 2.something MB of universal link data, along with any other link data from any other apps, would be queried for a relevant link if you clicked on any link in Safari, Mail, etc. The attempted handling of all of that data apparently corrupted a file at a low level, which means that once the damage was done, it needed this patch to address. Uninstalling the Booking.com app, once the issue had been triggered, did not solve anything.
 
This affected people people on earlier versions of iOS.

Clicking links in Safari, Mail and Apps is how I use my device for work aside from it being a phone. I'm glad its usable again now.
Wait, but weren't you putting the issue in the context of the iOS 9.3 release and its beta process?
[doublepost=1459452925][/doublepost]
There have been all kinds of bugs with iOS. This is the first that rendered my device unusable for 6 days.

What MTBF are you satisfied with?
So this is the first one that truly had a substantial effect. So I would say the comparable likelihood or frequency of something like that wouldn't change given that it's already been rather low given that this is the first one of such level you've experienced.
 
iPhone 6plus - bug did not show
iPad Air 2 - bug showed

Bookingdotcom - was once installed but removed from both devices at some point long before 9.3

Some sort of plist or cache for the app must still have caused the issue on iPad Air2. Not sure why iPhone was spared.

As for software freeze. I just can't see in today's climate of always adding features to keep users, stockholders and market share happy and growing that any company could do that. Bugs are going to get released. Known or unknown. It's just how things have become.

Every platform, every vendor, every device being created will suffer some form of an issue. Millions/Billions lines of code. Millions of programs/apps. Billions of devices. Billions of parts.

Tbh it's amazing that it all holds together as well as it does from concept to production to end user. One tiny defect in raw materials, programming, assembly, shipping, use etc can ripple thru in ways no one can predict.

I work as a technology integrator and use a wide array of products and manufacturers. I run into issues and problems daily as unexpected cases arise where something in the system has unexpected behavior. You work thru it, try to replicate and move on.

Technology is not infallible, people are not infallible. Expecting perfection on this scale is not realistic.
 
Wait, but weren't you putting the issue in the context of the iOS 9.3 release and its beta process?
[doublepost=1459452925][/doublepost]
So this is the first one that truly had a substantial effect. So I would say the comparable likelihood or frequency of something like that wouldn't change given that it's already been rather low given that this is the first one of such level you've experienced.

We've retreading here. You know where I stand on this. This bug showed that Apple needs to make changes to its Q/A process.

First one that lasted for 6 days. That shouldn't happen again for a very long time...
 
We've retreading here. You know where I stand on this. This bug showed that Apple needs to make changes to its Q/A process.

First one that lasted for 6 days. That shouldn't happen again for a very long time...
I think many things can be said to show that improvements can be made, including this bug in some sense. But what that won't do is eliminate something like this from happening at some point as there will always be some bugs somewhere that can end up becoming big for one reason or another. And given that the frequency of this type of issue has been basically 1 in all these years for you, it would seem that nothing out there would really improve those odds (as they would never practically go down to 0 from that 1).
 
I'm impressed that Apple fixed it. I'm glad the fix works. But let's talk about how we got here.

This happened because iOS development is rushed so that a new version is released every year. There's no need for it.

I don't want lunch. I don't want money. I want a public statement from Tim/Craig that changes will be made to improve the quality of Apple's software and the Apps on it... and the way you do this is to freeze development on all new features for a year so that the iOS team can do a top/bottom review of the existing code base without having to focus on new features.

I remember a particularly gifted history teacher explained that the German military success in World War II owed a lot to the fact that Germany had been prohibited from manufacturing arms in the period after World War I. Much of what remained of their arsenal post-war was destroyed, so they had very little old stuff lying around. They couldn't build new, which meant they had nobody saying, "We just manufactured 1,000 tanks a few years ago, we can't afford to build a new model now!" They could design, refine, trash, and repeat, at relatively little cost. When Germany was finally free to start building, they were decades ahead of their adversaries - everything was latest-generation. But there was one other key factor to all this; Europe was at peace. Germany had defensive forces, but didn't have to use them, or re-arm them.

Presumably, Apple could follow this same path. They could stop building and releasing new product until they reach perfection, then "Look out, world!" Instead of masses of users and app developers pounding on iOS and OS X in unimaginable ways until they trip over hidden flaws, we'll let a few thousand engineers in Cupertino do the job for them. If Samsung wants to continue releasing new product, no problem. If Wall Street demands a competitive response from Apple, the hell with 'em. If Apple's customer's switch to the competition because they want to replace their old equipment with the latest model, no big deal. In the end, what Apple builds will be so perfect, it'll be unstoppable!

One aspect of this particular issue is that it involved web browsing. Anybody on earth (or in orbit) can build a web site. There's no assurance they'll do a good job of it, or will follow standards, and they may intentionally violate standards. It's the Wild West - there is no enforcement. Basically, a browser has to be able to swallow anything thrown at it. If anyone believes it's possible to anticipate all the possibilities...
 
The OTA update to 9.3.1 appears on all of my devices Except my 6s. Why is that happening?
 
I love the apple goodies, but their ignorance at admitting issues/bugs is just insane.
People seeking for support in the past days were still hearing stupid default advice instead of real support: "Yes sorry, we are aware of a big problem. Look for the latest update on this issue apple.com/linkingproblem" or something similar.
 
  • Like
Reactions: Benjamin Frost
The bug that lets you bypass animations still works :D.
Important stuff.
[doublepost=1459455730][/doublepost]
If Apple came up with a development process that prevented "errors like this" that would be an enormous breakthrough in computer science that would dwarf anything they have ever accomplished. As far as anyone can tell, such a development process is unachievable. Every significant bit of software you have ever used has bugs. That has always been true, and likely always will be.

Possibly. Currently the software development cycle release is driven by the hardware release. As things get more complex this is a very tough model to sustain.
 
  • Like
Reactions: dysamoria
Well, this time I can actually say Safari is snappier ;-)

Still, quite disappointing that Apple didn't apologise for making my iPad unusable for 6 days.
 
  • Like
Reactions: Benjamin Frost
...there was an issue and released a patch. On Android, you'd be waiting months for a fix...

That depends on the method. If it is an Android System update, those can be rolled out via the Play Store. If it is an OS update, hopefully you are running a Nexus. If not you may never see it.
[doublepost=1459456130][/doublepost]
Oh, sorry, didn't know we were in English class.

One should always be aware of the "Grammar Nazi's".
Then tend to circle from time to time. :eek:
 
Heres to hoping it also address battery life issues.
I thought it was just me. 5S battery life has been seemingly cut in half on my 5S since I installed 9.3. Checked the battery usage in the preferences, but the percentage by apps is similar to what is was before, so it must be something in the OS itself.
 
I love the apple goodies, but their ignorance at admitting issues/bugs is just insane.
People seeking for support in the past days were still hearing stupid default advice instead of real support: "Yes sorry, we are aware of a big problem. Look for the latest update on this issue apple.com/linkingproblem" or something similar.
People were given some workarounds that have worked for some while being told that Apple is aware of the issue and is working on a fix.
 
So freakin buggy. Not showing recent calls. Apple watch is a week behind on recent calls. Many graphical problems. What a mess. I know Android isn't better, but man, this is the new Apple? iOS 6 and earlier were never like this.
 
  • Like
Reactions: dysamoria
So freakin buggy. Not showing recent calls. Apple watch is a week behind on recent calls. Many graphical problems. What a mess. I know Android isn't better, but man, this is the new Apple? iOS 6 and earlier were never like this.
All those threads from iOS 6 and earlier days that filled up the forums with all kinds of complains were just imaginary, right?
 
  • Like
Reactions: Codeseven
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.