You're not, but it's a public forum, so please respect good grammar. Thank you.Oh, sorry, didn't know we were in English class.
You're not, but it's a public forum, so please respect good grammar. Thank you.Oh, sorry, didn't know we were in English class.
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.
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.
How many times have you experienced an issue of this type with iOS?Would it happen more or less frequently after a feature freeze and a top/down review of the code base for a year?
How many times have you experienced an issue of this type with iOS?
Wait, but weren't you putting the issue in the context of the iOS 9.3 release and its beta process?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.
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.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?
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.
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).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'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.
Yes, it is. You would be waiting months for a fix on Android.Reasonable time? Is 6 days reasonable?
By the way, an anonymous PR drone acknowledged the issue. I've yet to hear Tim or Craig make any kind of statement.
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.
...there was an issue and released a patch. On Android, you'd be waiting months for a fix...
Oh, sorry, didn't know we were in English class.
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.Heres to hoping it also address battery life issues.
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.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.
All those threads from iOS 6 and earlier days that filled up the forums with all kinds of complains were just imaginary, right?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.