Gotcha, disregard then!
9.3.1 13E238 for a 6s Plus, if anyone wants to start the new list...
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
9.3.1 13E238 for a 6s Plus, if anyone wants to start the new list...
During all the betas the app (or rather the specific version of it) that triggered this wasn't available yet. You cannot test for incompatibilities with not yet existing software. They could have caught the bug by thinking harder of what might happen if X occurs. But the problem wasn't testing (yes, they could have thought of tests that could have caught this but no testing will ever be able to test nearly all imaginable situations, there are just to many possible permutations).
Didn't know that, I figured it was reboot because the second line always goes much faster and usually the device turns on before its 100% completed.
Glad this was fixed. Although, it did take over 5 seconds for Safari to launch after I tapped on a link in an email for the first time after the update was installed. It almost had me thinking #FAIL, because the Mail app was unresponsive during that time. All subsequent link tapping launched Safari immediately. Makes me wonder if there was some sort of post-install processing done once you tap that first link after the update.
I had the problem in a major way, links in Safari, Mail, even Bing and Chrome to a degree.
The weird thing is that it didn't surface until about 4 days after I installed 9.3, and I definitely would have noticed if it had been going on from day 1.
Because of that, i deleted, all the apps that had updated between 9.3 download and the problem surfacing. That had no effect.
The good news is, I just installed 9.3.1, and so far so good. I tested some links in Safari and Mail and they work fine.
The weird thing is that it didn't surface until about 4 days after I installed 9.3, and I definitely would have noticed if it had been going on from day 1.
Because of that, i deleted, all the apps that had updated between 9.3 download and the problem surfacing. That had no effect.
The good news is, I just installed 9.3.1, and so far so good. I tested some links in Safari and Mail and they work fine.
Yeah I heard they were still looking for your phone # and email address to personally send you your apology. Sorry could not resist.
I saw where that's what YOU wanted from Apple. And Android would have been 6 months (or more) not days.
Last edited:
Yes, 6 days is reasonable when any change has to be tested to make sure it doesn't break something else.
The reality is that for a complex and large scale OS it's not an unreasonable amount of time.
And, yes, the reality is that that's how most companies handle most of those types of issues where they comment to a news source about the problem and that they are working on it and that they hope to fix it as soon as possible, and that's for those that even bother to say something about it as many don't on many occasions. That's the reality of it (vs utopia).
Me too. Wait till this weekend when off work. That way if it screws up I have a full day to deal with it. Just like the preview update that temporarily failed my iPhone's and iPad. Shoddy work Apple.
Two ****ing GBs AGAIN!? They really need to get their **** together. Something is seriously wrong in the software department.
Last edited by a moderator:
It was there before the recent update and it's betas. Bugs will happen, there's practically no escaping that reality.
What battery life issues? Mine has been incredibly good since 9.3.
OTA is 35~MB? No? My 6s and Air 2 were both 35.3MB.
There was massive background battery usage. There is a thread in iOS 9 category about it.
Last edited by a moderator:
Mine was only 35.3MB on the 6s Plus. Maybe you are on the public beta still or something is wrong...
Last edited by a moderator:
Yeah I heard they were still looking for your phone # and email address to personally send you your apology
I don't want money. I don't want a personal apology. I want a public statement from Tim/Craig to all customers that they are changing their iOS development process to prevent errors like this in the future, whether it's from iOS or the Apps.
Again, Apple should freeze the iOS feature set for a year, and focus on quality/reliability only. Bug fixes and security improvements. That's it. I don't need MORE FEATURES!!!
Reliability is a feature. Apple has forgotten that IMHO.
Well I mean, if you want to go and implement the fix yourself AND test the whole OS to make sure everything is okay, be my guest, oh and take no longer than one week please. Go on, off you go.
This wasn't an issue present in any of the betas, it was a brand new bug and it's fixed already. Show them a bit of credit.
You're wrong on that. Users reported this to Apple during the beta period. It was ignored. "Screw it. Ship it."