Apple Working on a Fix for iOS 9.3 Web Links Crashing Issue

[robeddie]

LOL. Do you not remember OS X 10.0? So bad they had to give away 10.1 to restore missing features, like DVD players and CD burning? And then the fact that it had tons of bugs that resulted in Kernel Panics....
Let's take a trip down memory lane:
http://archive.arstechnica.com/reviews/01q2/macos-x-final/macos-x-1.html

I didn't come to the Mac until 2002 and 10.0 was BAD! 10.1 wasn't much better but serviceable...

I thought you might come up with 10.0 as an example. But as you know then, at that point in time of the major os transition, people had the rock solid os-9 to fall back on. Any major os tranitions are going to be rough and thats to he expected, but Apple didnt expect people to use the earliest versions of osx as their main system, as all macs at that time could boot into os 9 as well.

In fact, well into 2003, two years after the release of 10.0 (and well after the release of the fairly solid 10.2 'Jaguar') new macs sold could still natively boot in os 9.2.2. So its wasnt like Apple was hanging you out to dry with a buggy os.

Nowadays we're talking about nasty bugs in even minor incremental software updates - a far cry from a massive os transition. So to compare osx 10.0 to this is, imo, completley daft
[doublepost=1459335239][/doublepost]

Many people don't really actually know the past, forgot the past, or just ignore the past...all while trying to draw some sort of conclusions and come up with some sort of theories referencing simply what they wish or think it was (rather than what it actually was).

Given what I explained above, I would contend its him, not me, who is distorting 'history' to suit his bias.

 

[true god]

Their quality continues to decrease. Apple is on the verge of becoming Microsoft; too big to do everything right.

Best way to make people upgrade is to make their old device unusable if only for a little while.

 

[IPPlanMan]

Best way to make people upgrade is to make their old device unusable if only for a little while.

Best way to make people leave is to make their iPhone 6s unusable for 5 days now.

I really hope this fix comes today with an apology tweet from Tim and Craig (that's right I said it) that they'll do better going forward.

 

[Azzin]

oh, I'm also a CURRENT Microsoft user, for what it counts...
But you were totally wrong about me: Apple user since 1989/90, my first Mac was a Macintosh IIx, I switched to an "all Macs ecosystem" back in 2005. I think I know Apple better than most here...
We live in a different time, Apple is not the same and it can't be.
The old philosophy doesn't apply today. I don't like an OS X yearly upgrade policy, for sure (2 years seem better to me), but regarding iOS they are right.


A man that hardly had written a single line of code....


it was a combination of poorly written apps and a subtle iOS bug.

You ''know Apple better than most here"?

You've been using their products for a reasonably long time, but you don't ''know' anything about Apple, because you're not Tim Cook, or any of the inner circle of those that do genuinely 'know Apple".

Thanks for making me smile though.
[doublepost=1459342129][/doublepost]

Best way to make people leave is to make their iPhone 6s unusable for 5 days now.

I really hope this fix comes today with an apology tweet from Tim and Craig (that's right I said it) that they'll do better going forward.

And if/when that doesn't happen, you'll do what?

Nothing I would guess, like the vast majority of people who accept that these mobile computers we call the iPhone, are very complex beasts and experience glitches from time.

I'm a vote with your wallet guy and if it bothered me that much, I'd ditch Apple in a heartbeat.

However, it doesn't bother me that much, so I shrug, wait for Apple to issue a fix and get on with my life.

Build a bridge and get over it, poop happens.

Fancy moving to Samsung/Android?

 

[IPPlanMan]

and yet there are 7 beta build released for 9.3

It didn't matter because the development cycle was rushed and the testing protocol was insufficient leading up to 9.3

This will only get fixed when Apple decides to get away from annual iOS updates, which pressure developers and testers into having rushed quality control cycles. I don't need annual iOS Updates. I want reliable iOS updates.

Freeze the iOS feature set for a year. Do only Bug Fixes and Security updates. Focus on reliability. Everything else is window dressing. Reliability sells. Reliability is a feature.

Tim and Craig need to get a clue, admit/apologize for the issue and fix the problem. That's what I want. I don't want money. I want an apology and acknowledgment that things will change going forward.
[doublepost=1459342545][/doublepost]

You ''know Apple better than most here"?

You've been using their products for a reasonably long time, but you don't ''know' anything about Apple, because you're not Tim Cook, or any of the inner circle of those that do genuinely 'know Apple".

Thanks for making me smile though.
[doublepost=1459342129][/doublepost]
And if/when that doesn't happen, you'll do what?

Nothing I would guess, like the vast majority of people who accept that these mobile computers we call the iPhone, are very complex beasts and experience glitches from time.

I'm a vote with your wallet guy and if it bothered me that much, I'd ditch Apple in a heartbeat.

However, it doesn't bother me that much, so I shrug, wait for Apple to issue a fix and get on with my life.

Build a bridge and get over it, poop happens.

Fancy moving to Samsung/Android?

I won't leave, but I won't buy or recommend additional Apple products for mission critical purposes if they can't be used that way. Apple is not a "five-nines"(https://en.wikipedia.org/wiki/High_availability) company and that's a shame, because it easily could be with better focus and processes.

Apple needs to make things less complex and more reliable. Unfortunately, reliability is no longer a priority for the company.

 

[Max(IT)]

You ''know Apple better than most here"?

You've been using their products for a reasonably long time, but you don't ''know' anything about Apple, because you're not Tim Cook, or any of the inner circle of those that do genuinely 'know Apple".

Thanks for making me smile though.

I know Apple as a user. Don't need to be Tim Cook for that. I don't need to work for Apple. I just need to buy their products.


Reasonably long time ? Lol, do you realize that Cook was hired in 1998 ? I was an apple user for almost 10 years then.... I can consider myself a long time Apple user.

 

[Azzin]

I know Apple as a user. Don't need to be Tim Cook for that. I don't need to work for Apple. I just need to buy their products.

You (like the rest of us) know just what Apple want you to.

Nothing more, nothing less.

Reasonably long time ? Lol, do you realize that Cook was hired in 1998 ? I was an apple user for almost 10 years then.... I can consider myself a long time Apple user.

Yay you.

Do you want a medal or something?

It doesn't make you in any way cooler because you used Apple products before most and before Tim Cook.

 

[Max(IT)]

Yay you.

Do you want a medal or something?

It doesn't make you in any way cooler because you used Apple products before most and before Tim Cook.

It makes me happy. And proud. And that counts for me.

 

[zup]

This is not an ios 9.3 bug, it happens on 9.x, the timing was bad with the booking.com app screw up that got triggered around same time as 9.3. Stop spreading false rumors.

 

[IPPlanMan]

This is not an ios 9.3 bug, it happens on 9.x, the timing was bad with the booking.com app screw up that got triggered around same time as 9.3. Stop spreading false rumors.

I'm not spreading any false rumors. I'm saying that Apple's QA process is totally inadequate and they need to put the brakes on all new iOS features for a year until they sort this out with a top down review and audit of the existing code base and App set.

I'm at 5 days with an unusable device (iPhone 6s). This is beyond laughable. Apple needs to do right by its customers: I don't want money. Tim and Craig need to take responsibility, issue a public apology for this and change the entire software development and quality assurance process at Apple. It's broken, and it will, mark my words, happen again unless big changes are made.

 

[C DM]

It didn't matter because the development cycle was rushed and the testing protocol was insufficient leading up to 9.3

This will only get fixed when Apple decides to get away from annual iOS updates, which pressure developers and testers into having rushed quality control cycles. I don't need annual iOS Updates. I want reliable iOS updates.

Freeze the iOS feature set for a year. Do only Bug Fixes and Security updates. Focus on reliability. Everything else is window dressing. Reliability sells. Reliability is a feature.

Tim and Craig need to get a clue, admit/apologize for the issue and fix the problem. That's what I want. I don't want money. I want an apology and acknowledgment that things will change going forward.
[doublepost=1459342545][/doublepost]

I won't leave, but I won't buy or recommend additional Apple products for mission critical purposes if they can't be used that way. Apple is not a "five-nines"(https://en.wikipedia.org/wiki/High_availability) company and that's a shame, because it easily could be with better focus and processes.

Apple needs to make things less complex and more reliable. Unfortunately, reliability is no longer a priority for the company.

And it still doesn't really have anything to do with the iOS 9.3 release or its beta process.

 

[jfiggy77]

I beta tested every version of 9.3 and the issue started for me with Beta 3 or 4....I can't remember exactly. I submitted beta feedback to Apple describing this same issue as soon as I noticed it during beta testing and never got a response back. I even started a post here on MacRumors about this very issue on March 6, two weeks before 9.3 was released. Here is my post: https://forums.macrumors.com/thread...n-mail-safari-and-news.1959917/#post-22712209. I thought I was alone with this problem. After numerous reformats and downgrades to 9.2 were I also experienced this issue so it's not just a 9.3 issue, I stumbled across a post on the Apple forums right after the 9.3 update from someone who was having the very same issue as me.....that forum post is now 53 pages long. This was definitely an issue in the betas. Had they caught it then, they would have released 9.3 without this issue. Had someone responded to my beta feedback, they would have known about it then. I have both an iPhone 6s Plus and an iPad Air 2 LTE and both ran the betas. My iPad 2 just started experiencing this issue this past weekend when I opened the Booking.com app for the first time. I had it installed on the iPad but had never opened it. As soon as I opened it, the iPad started having the links issue. Hopefully we'll see something this week or very soon because it affects so many aspects of the OS.

This is not an ios 9.3 bug, it happens on 9.x, the timing was bad with the booking.com app screw up that got triggered around same time as 9.3. Stop spreading false rumors.

 

[C DM]

I'm not spreading any false rumors. I'm saying that Apple's QA process is totally inadequate and they need to put the brakes on all new iOS features for a year until they sort this out with a top down review and audit of the existing code base and App set.

And while there is a point there and improvements could and should be made, issues like this one will still come up from time to time nonetheless.

 

[IPPlanMan]

And it still doesn't really have anything to do with the iOS 9.3 release or its beta process.

Sure it did. The software had a fundamental flaw if something like this could happen. 9.3 didn't have to be released. This bug should have been caught a long time ago and efforts were so focused on useless window dressing features for 9.3 that things like this were missed.

Ultimately, this falls on Tim and Craig's shoulders. They set the tone and policy. They own it and should admit it.
[doublepost=1459349123][/doublepost]

I beta tested every version of 9.3 and the issue started for me with Beta 3 or 4....I can't remember exactly. I submitted beta feedback to Apple describing this same issue as soon as I noticed it during beta testing and never got a response back. I even started a post here on MacRumors about this very issue on March 6, two weeks before 9.3 was released. Here is my post: https://forums.macrumors.com/thread...n-mail-safari-and-news.1959917/#post-22712209. I thought I was alone with this problem. After numerous reformats and downgrades to 9.2 were I also experienced this issue so it's not just a 9.3 issue, I stumbled across a post on the Apple forums right after the 9.3 update from someone who was having the very same issue as me.....that forum post is now 53 pages long. This was definitely an issue in the betas. Had they caught it then, they would have released 9.3 without this issue. Had someone responded to my beta feedback, they would have known about it then. I have both an iPhone 6s Plus and an iPad Air 2 LTE and both ran the betas. My iPad 2 just started experiencing this issue this past weekend when I opened the Booking.com app for the first time. I had it installed on the iPad but had never opened it. As soon as I opened it, the iPad started having the links issue. Hopefully we'll see something this week or very soon because it affects so many aspects of the OS.

And there you have it.
[doublepost=1459349281][/doublepost]

And while there is a point there and improvements could and should be made, issues like this one will still come up from time to time nonetheless.

Time to time... What's time to time? 5-Nines Time to Time or more frequently?

Reliability is apparently no longer a feature Apple places as a priority. And that's a shame.

Take the engineers/resources that rushed to get window dressing features like Night Shift in there (which makes my screen look like I spilled coffee on it) and they should have frozen the feature set so that the existing code base could be fully reviewed.

That wasn't done... and here we are.

 

[C DM]

Sure it did. The software had a fundamental flaw if something like this could happen. 9.3 didn't have to be released. This bug should have been caught a long time ago and efforts were so focused on useless window dressing features for 9.3 that things like this were missed.

Ultimately, this falls on Tim and Craig's shoulders. They set the tone and policy. They own it and should admit it.
[doublepost=1459349123][/doublepost]

And there you have it.

Except there not how software development works in reality, just in theory.

 

[IPPlanMan]

Except there not how software development works in reality, just in theory.

I don't want any Software Development for new features. Freeze the feature set completely. No new features for a year. Focus all resources on Quality/Reliability for the existing code base with security updates and bug fixes. That's what Apple needs to do.

 

[C DM]

I don't want any Software Development for new features. Freeze the feature set completely. No new features for a year. Focus all resources on Quality/Reliability for the existing code base with security updates and bug fixes. That's what Apple needs to do.

And as mentioned many times before, it will certainly help and improve things, but issues of this type would still happen nonetheless. There are no magical silver bullets that will somehow change reality.

 

[IPPlanMan]

And as mentioned many times before, it will certainly help and improve things, but issues of this type would still happen nonetheless. There are no magical silver bullets that will somehow change reality.

Nothing is ever perfect. However, you'd have to admit that this situation is completely unacceptable. Silver bullets aside, you agree with me on this and it sounds like you'd support it.

Tim and Craig could march into the iOS Team one day and say: "We're freezing the feature set and halting all additional development for a year to focus on quality/reliability. Starting now we're doing a top to bottom review of the entire code base and app vulnerabilities.".

The team would do it. That's reality. Reality is also that Tim and Craig haven't done that... and that's a shame.

 

[C DM]

Nothing is ever perfect. However, you'd have to admit that this situation is completely unacceptable. Silver bullets aside, you agree with me on this and it sounds like you'd support it.

Tim and Craig could march into the iOS Team one day and say: "We're freezing the feature set and halting all additional development for a year to focus on quality/reliability. Starting now we're doing a top to bottom review of the entire code base and app vulnerabilities.".

The team would do it. That's reality. Reality is also that Tim and Craig haven't done that... and that's a shame.

I support it, as I've mentioned a number of times before. I'm simply pointing out that we'd still run into issues of this type at one point or another nonetheless.

 

[IPPlanMan]

I support it, as I've mentioned a number of times before. I'm simply pointing out that we'd still run into issues of this type at one point or another nonetheless.

Apple isn't close to being a 5-Nines company. (https://en.wikipedia.org/wiki/High_availability). It either wants to be or it doesn't. If it doesn't, then it should say so. Right now we're approaching 98%.

 

[C DM]

Apple isn't close to being a 5-Nines company. (https://en.wikipedia.org/wiki/High_availability). It either wants to be or it doesn't. If it doesn't, then it should say so. Right now we're approaching 98%.

What OS companies are?

 

[IPPlanMan]

What OS companies are?

Apple isn't just an OS company. It's a hardware company. It's a services company. It's a company that marches to the beat of its own drum and stands alone for superior design and ease of use over the competition.

I'm holding Apple to a high standard because that's what it advertises itself as: The best

If other companies aren't, then Apple should be.

I'm not content with the status quo either. Apple can and should do better. What a let down.

 

[nazaar]

This has been happening to be since before 9.3

 

[C DM]

Apple isn't just an OS company. It's a hardware company. It's a services company. It's a company that marches to the beat of its own drum and stands alone for superior design and ease of use over the competition.

I'm holding Apple to a high standard because that's what it advertises itself as: The best

If other companies aren't, then Apple should be.

I'm not content with the status quo either. Apple can and should do better. What a let down.

So, again, basically theory over actual reality.

 

[IPPlanMan]

So, again, basically theory over actual reality.

There's no theory here. Reality is Apple can and should do better. I've explained how it's possible.

Or are you saying that Apple can no longer put a dent in the universe?
[doublepost=1459353514][/doublepost]

This has been happening to be since before 9.3

Which is why it's all the more embarrassing.