Wow, I ran Yosemite for a year and am running El Capitan right now and my Wi-Fi has never dropped out, get a new router or something.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases iOS 9.3.1 With Fix for Web Link Crashing Bug
- Thread starter MacRumors
- Start date
- Sort by reaction score
Wow, I ran Yosemite for a year and am running El Capitan right now and my Wi-Fi has never dropped out, get a new router or something.
One of the most critical aspects of software development is being able to reproduce a reported problem. If a problem cannot be reliably reproduced, either because of insufficient reproduction steps in the problem report, or complete lack of reproduction steps, simply reporting the existence of an issue is not always enough to be able to properly address it.
Without knowing more about said previous reports of this issue, I find it difficult to just assume that they provided adequate steps to reproduce, especially after hearing about the finer details of the conditions that triggered this issue.
See here: https://forums.macrumors.com/thread...s-crashing-issue.1964477/page-9#post-22739147
It was reported to Apple.
mine is stuck on the "download and install" with the spinning wheel.. I rebooted my phone too and nada
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.
Ah yeah, further shows you how pointless sending feedback to Apple is.
I have open and unanswered bug reports sitting in my radar account that are months old.
Dare I guess some may even have their first birthday soon.
Glassed Silver:mac
Imagine if ANY of the iPhone Se's or new iPad pro's had this issue.
Apple would definitely have to officially address the public and not just reporters.
Apple would definitely have to officially address the public and not just reporters.
Interesting, Notice that particular one was initiated by the booking.com app. Which seems to be a common denominator for folks experiencing the issue. Also seems it wasn't very widespread according to the poster you quoted.
Reproduction steps is the path to addressing/fixing the bug. But does not speak to awareness that the problem exists. If they chose to release a software update out to the general public, knowing that a bug of such significance exists in the update... that seems very irresponsible. Could they not have chosen to wait before releasing the update, while they tried to figure out the problem? As a user affected by the problem... i 100% would have preferred to stay on the older version of software than update and have the bug.
So, you know for a fact that this fix is a workaround, rather than directly addressing the cause? You're saying that there would be no clues to the cause in a crash log? That nobody posted evidence of a potential cause?
...The exact underlying cause of the problem has not been discovered...
I'd suggest a more accurate statement would have been, "The exact underlying cause of the problem has not been disclosed..." Developers rarely, if ever, disclose what lines of code had to be changed, and what those changes were, unless it's open source (and iOS is not open source).
I'd suggest this release is evidence that the cause of the problem has been discovered. It was not such a widespread issue that Apple needed to release an emergency fix. Considering all the implications of issuing a new OS release, would releasing a half-baked workaround been the right approach?
Steve would have had a head or twenty rolling for repeated releases of flawed operating systems
That's a judgement call left for the fellows at Apple, who have way more data in their hands to use to come to that decision than anybody else. However, with the benefit of hindsight, one could conclude that it was the wrong choice.
I will add that I used to do development for a living for five years right out of college. I was one person responsible for just over 5 million lines of C++ code. Needless to say, I quickly succumbed to burn out (5 years is quick to me.) Programming for a company with the exposure and size of Apple is not something that should be considered an easy going gig. It sucks. Companies such as that have very tight deadlines, with staff that are usually largely overworked, and arguably somewhat under appreciated (at least going from the reaction in these forums.)
Anyway, out of the people on these forums that claim to have reported this issue to Apple during the 9.3 beta period, I have yet to see a single one that states that they included reproduction steps. I cannot stress enough how critical it is to provide those in order to effectively resolve an issue as expeditiously as possible.
Last edited:
Newer devices seem to have a smaller file size. It was 101 MB for my 4S. Weird.
There's always going to be bugs with new software. What I'm interested in is prompt fixes and Apple have an excellent track record of pushing out fixes in a timely manner.
