Replicate how? Did you install Booking.com app, for example?
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.
Web Links Crashing Safari, Mail, Chrome, and Other Apps on iOS 9.3 [Updated]
- Thread starter MacRumors
- Start date
- Sort by reaction score
here:
https://forums.macrumors.com/threads/ios-9-3-links-in-safari-not-clickable-anymore.1962471/
And you're right. Not wit. Sarcasm.
No, I don't use Booking.com. I tried mail-links and links in Safari. Didn't get that the problem was related to installation of specific apps. The possibility is that this is caused by bad coding in third-party apps.
Hardly moot. If the bug was idenitified and ignored during the beta process, that is a failure of the process regrdless of how many ios versions it affects.
Is that sarcasm too? Hard to tell.
Surely you cant be defending Apple's beta process when thousands of devices have been crippled.
Sent from my iPad using Puffin cos the native browser doesnt work
Doesn't quite seem like it was. And, again, it's not related to iOS 9.3 itself as it affects earlier versions too.
I wasn't being sarcastic... I honestly believe Apple has developed a "screw it, ship it" attitude with Betas. For example, Night Shift could have been released in 9.3.1 instead, but oh no, it had to be crammed in there to make some Project Manager's schedule in order to make him/her look good to upper management.
Doesn't seem like it was identified during the beta process. Some mention that someone encountered something similar on and off, but unclear that it's the same issue or that it wasn't something unique to that user or device or that it was even reported or how much of an impact it had overall. Certainly assumptions and theories, but doesn't seem like there's anything to really back things up aside from what people actually started running into last week.
[doublepost=1459203366][/doublepost]
And how was it crammed into it or what effect it had on any of this?
[doublepost=1459203410][/doublepost]
Well, it seems that's one of the ways the issue has been replicated. Simply using links doesn't really replicate things as not all devices are affected by this.
My Samsung Galaxy Note 4 is also doing fine but how is that really relevant? Did anyone claim that the problem affected all iPhones at once?
Fair call. Well put.
[doublepost=1459203792][/doublepost]
oh right. I thought you meant "screw it" = insert a bug in the OS and then ship it. My bad.
Because the more features crammed into a single point release, the less thorough the Beta Testing is. If this was recurring in the 9.3 Betas all extraneous features needed to be removed and released as 9.3.1 or 9.3.2
iOS 9.3 wasn't "Snow Leopard"... In fact, it was the exact opposite.
I keep hearing Jobs say: "We operate like the largest startup on the planet."
This is so amateur
This is so amateur
I don't see the part where the poster reported the bug to Apple.
That would be relevant if this bug had anything to do with 9.3.
Again, this issue affects iOS 9 versions prior to iOS 9.3, so even if there wasn't a 9.3 release, it seems that the issue would still be there affecting people.
[doublepost=1459204496][/doublepost]
Well, to be fair, startup or large company, issues like this pop up here and there.
This bug has everything to do with anything Apple in my opinion. It's a symptom of a larger underlying issue at Apple in terms of Apple's iOS Software Quality: "Screw it, Ship it" has become the new attitude, and that's a shame. Getting back to a "Snow Leopard" attitude is where they should be. Smaller, iterative, well-tested improvements should be the focus.
Apple needs to slow its roll on having so many features at one time and actually have a stable Software Release for a change. I was quite happy on the prior version of iOS, but Apple had to meet some self-imposed schedule and skimp on thorough Beta Testing here.
Apparently, Apple didn't learn enough from the 8.0.1 rollout which disabled Touch ID and Cellular Connectivity.
[doublepost=1459204645][/doublepost]
Ok, so the bug was there all along. What does that tell you?
Meanwhile, I am here on a 6s and AVOID being lab rat by waiting out.
Thanks for letting us know it works for you. That represents one case of positive in the survey of hundreds and thousands of 6s owners.
That it doesn't have much to do with iOS 9.3 or anything that was "crammed" into it or anything like that.
Also, the issue with iOS 8.0.1 didn't have anything to do with iOS itself, so it's another unrelated example essentially.
Last edited:
9.3 is precisely an example of "smaller, iterative, well-tested improvements". They could have crammed the features of 9.1, 9.2 and 9.3 into 9.0, or wait another cycle and cram then into 10.0. Instead, they opted for smaller iterations.
It tells us that the bug is so obscure that over a year of cumulative alpha, developer and public beta testing did not track it down. It tells us, ultimately, that the quality problem can't be that big, since otherwise, it would've appeared much sooner.
It didn't have anything to do with the iOS? Why does that matter? It was called iOS 8.0.1 and it rendered many devices unusable. It doesn't matter to me if it was part of the software itself or if it was a deployment issue. Apple still had a major screw-up.
[doublepost=1459205383][/doublepost]
No it isn't. 9.3.1 or 9.3.2 would have been iterative.
Here we are on Monday evening and still not a single official word from Apple about it. Yes, that's a sign of a big problem.
It matters because you keep on tying it to "cramming" issues and beta cycles and getting things out before they are ready to meet marketing deadlines, when these issues are not related to those items. What you are talking about has a point to it, it's just that the things you relate to it and use as examples aren't really the ones that demonstrate it.
So true. This what is so pathetic.
[doublepost=1459205829][/doublepost]
What exactly are you defending? We agree that Apple has made a monumental mistake, yeah?