sucks to be apple, right now. They are having a bad week!
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 Working on a Fix for iOS 9.3 Web Links Crashing Issue
- Thread starter MacRumors
- Start date
- Sort by reaction score
Apple needs to stop adding features and start adding reliability.
And that still won't ensure that issues of this type won't pop up at some point.
I don´t think there are more bugs. It´s rather that every iOS bug is news now. But in this case Booking.com is to blame as they added all their hotel urls (yes, every hotel in their database, 2.3MB total) to Safari universal links.
Apple needs to be a "5-Nines" company. It's far from it now. Fundamental changes are in order. New features need to be frozen and a complete top-down quality review of iOS 9.3 needs to be done. That's not to say that errors won't occur in the future, but something like this shouldn't happen again for a long time.
Let's say that I have to wait for 9.3.1... Let's say it's not out until Friday. That will be 7 days without being able to use Safari on my iPhone 6s for my work and mission critical purposes. That's disgraceful and Apple should be ashamed.
[doublepost=1459280140][/doublepost]
And it's Apple's fault for not anticipating this might happen with Universal Links. Did no one in Software ask: "Gee, what happens if the Safari Universal Links gets flooded with URLS"?
[doublepost=1459280222][/doublepost]Just what we need... 9.3.1 to be rushed out the door before it's fully baked to "fix" an issue.
"Fine grained internal testing" is exactly the approach that does not find problems such as this. These problems manifest when an application uses a combination of features, in a variety of configurations, which is the opposite of "fine grained". Apple can test certain combinations and representative applications; but the permutations can run into the billions or more. Hence the need for Beta tests, which allow users to exercise the product under the combinations that they use. I would guess the particular combination of events that set this off was not exercised by users, or not reported.
The world also needs world peace. Many have been striving for it, but the results have been pretty obvious throughout history.
That said, you are unhappy about and counting days without a fix, and at the same time talking about that it doesn't make sense to rush it.
Just, download/update Booking.com they have fixed their app and turn off JavaScript until the fix comes.
Because the freezing issue is the most urgent fix, and I don't want it appended to Apple's planned 9.3.1 coming in who knows when. I want the fix for this freezing issued today as 9.3.1.
9.3.2 needs to be a feature locked and thoroughly vetted update, and not rushed out the door in order to provide a fix for the freezing issue.
Is anyone getting the issue where notifications don't show up at all on lockscreen or at the top but display in the notification center? As well as that always at the same time, the volume display when you tap the volume buttons doesn't appear.
This version of iOS is ridiculously buggy for me...
This version of iOS is ridiculously buggy for me...
Anyone who needs their device for work or mission-critical purposes would not be upgrading to a new release until they have either tested it themselves or waited until the field reports come in. If they do, shame on them. And that would be THEIR fault for losing business.
I know in my own company, our IT department tests every new release for at least a couple of weeks before recommending an upgrade.
Do you actually use your phone in this way, or are you just conjecturing?
That fixes the issue with the Booking.com app. It doesn't fix the issue with web links.
That would be 9.3.1 as far as getting a fix out. They can issue a new 9.3 build perhaps instead, but seems like issuing 9.3.1 would be more straightforward as far as getting the update to everyone.
What, a bad week? No. They have acknowledged there's an issue and they are working on a fix. If the issue was present in the betas then fair enough. It's a brand new issue, they are fixing it.
Gasu, this is MR. So it's conjecture. Definitely conjecture.
Are you serious? So it's my fault that Apple didn't thoroughly test its software? I updated 24 hours after the release went out.
What's Apple selling me here? I thought it was selling me a rock solid iOS experience. Clearly this is no longer the case.
Yes, I actually use my phone this way.
It's a rock solid experience compared to Android. Go on then, off you pop...
You sir, are a GOD.
Uninstalling Booking.com didn't make the trick for me.
BUT:
Turning off Javascript, restarting Safari, visiting some links, then turning it back on, and my iPhone works perfectly!
EDIT: Nah, after 15 minutes it's back to the non-working link mode. Damn. I was so happy for a few minutes.
I don't expect more from Android. I expect better from Apple. I hope we all do.
Suggesting that I leave because I expect better from them means that I'm not part of the problem.
The Booking app seems to be the cause of the issue so how on earth out of the trillion of apps available were Apple to know that Safari wouldn't work? I don't have the Booking app and Safari has been working perfectly for me.
[doublepost=1459281357][/doublepost]
See post #47.
[doublepost=1459281357][/doublepost]
See post #47.
Heard of MS and Android - one week after a new software release? Just wait till you try any of that!
Last edited:
Thank you. There are a bunch of people commenting on the "quality control problems" at Apple when it comes to software who really should just shut the eff up. They have no idea that:
A. Bugs are going to happen no matter how much testing occurs before release.
B. This is likely a small bug that affects relatively few of the approx. 1 Billion users out there. And if they weren't watching MacRumors like a hawk they likely would not have even known it exists.
There are over 1.5 million apps available on the app store, and any one of them can cause a problem with the OS, no matter how thoroughly it was tested.
I updated my post: The freezing issue is the most urgent fix, and I don't want it appended to Apple's planned 9.3.1 coming in who knows when. I want the fix for this freezing issued today as 9.3.1.
9.3.2 needs to be a feature locked and thoroughly vetted update that 9.3.1 was originally going to be, and not rushed out the door in order to provide a fix for the freezing issue.
[doublepost=1459281685][/doublepost]
See what?