my iPhone 6 plus is affected, i disabled java to use the google search page, however can't open any link from my email!
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
I cant believe it is taking Apple so long to release an update. These laptop replacements are unusable!
Incorrect.
If it is a software issue, replacing the phone would be no better than you wiping your phone and setting up as new.
If you restore a replacement with your backup, the issue will be brought back.
So no, replacing the phone will not change it.
Applecare likely positioned a replacement to appease you because you dont want to restore your phone for some reason or another.
The problem is that the OS code won't even get that far. Once the database is broken, it crashes over and over trying to read it. The changes to Bookings.com only help if the database is still working.
Even that would only help future installations.
If nothing else, it breaks the promise of the sandbox that nothing from the App Store can screw up your system, only the app itself. In this case, it absolutely triggers a system-wide problem.
Apple still hasn't officially said anything yet today (and we're past 5PM ET). They haven't even acknowledged there's an issue, and I don't see them making an evening press release, which leads me to believe that we're at least 24-48 hours away from a fix rolling out.
Safari has been completely unusable on my iPhone 6s since yesterday, and the only way I can open links is to use Chrome and open a new tab for each link I want to view.
I've been a longtime Apple user, and this is beyond embarrassing at this point.
Apparently, Apple didn't learn anything since the 8.0.1 debacle, which disabled Touch ID and cellular connectivity on iOS devices.
Safari has been completely unusable on my iPhone 6s since yesterday, and the only way I can open links is to use Chrome and open a new tab for each link I want to view.
I've been a longtime Apple user, and this is beyond embarrassing at this point.
Apparently, Apple didn't learn anything since the 8.0.1 debacle, which disabled Touch ID and cellular connectivity on iOS devices.
Apple has shrunken their Quality Assurance team several years ago.
I'm not surprised to see **** like this happening all the time now.
Here I am just sitting and waiting for the day Apple actually gets punished in cold, hard numbers.
Nothing else will change their course as long as people keep buying more instead of less from Apple.
Glassed Silver:mac
I know it didn't start that way. My previous comment answers this exactly. You said that I was looking at iOS 6 in its end stage, but my point is that it reached its end stage a lot earlier than iOS 9. iOS 6 was finished and didn't need fixes after the six-month mark. We're at the same point in time with iOS 9 and it still needs major fixing. 9.3, which is supposed to be a fix has received its own major fixes already and will still get more. These are facts. Factually, at the point that iOS 6 reached its end stage, iOS 9.3 is being recalled and re-released. That itself is not an opinion. Maybe it's my opinion that it should be where iOS 6 was.You're conflating my comment about your revised history of iOS6 with excuses for iOS9. My original comment to you had nothing to do with iOS9. It was a refutation of your comment about the stability of iOS6. It eventually became a more stable OS, but it didn't start that way.
Coupl'a things: 1. "iOS 9 should be at that stage by now, and clearly it's not. Factual." Factual doesn't mean what you think it does. That's an opinion. 2. Your keyboard may have something sticky under the 1 key. You typed an exclamation point and the key didn't lift until you had six showing. Compressed air or a wipe might help.
Everyone praise the "simplicity" of starting anew without any tools like a command line, diagnostics etc...
And the joy that is reapplying app data individually... Oh wait, that isn't even a feature.
That's what you get when you keep things too simple.
That's why I'll never look at iOS as anything more than a toy OS or one that may fill a need on the go, once the job is done, transfer the work to a real OS (OS X in this case, which still only supports archaic filesystems that don't even check file integrity... For ****s sake Apple, it's 2016...).
Glassed Silver:mac
Having to restore anew is a great tool for any OS.
Trying to repair Windows for instance, at a certain point, is a fools errand...
Apple knows about the issue as many support responses have pointed out. As far as a statement or anything like that, they might very well not make any until they actually put a fix into place.
I'm going back to my iMac more now. I simply don't want to rely on my iPad or iPhone when they're so unreliable with rubbish like this link crash. It's made me wary of iOS for work.
They've really screwed up with this mess.
Issues actually need to be investigated, a resolution needs to be arrived at, that resolution needs to be actually implemented, then it needs to be checked, etc. Magic isn't real unfortunately.
You shouldn't be FORCED to do it, but be free to chose a path that suits your situation best.
I'm not here to live for the OS, it's the other way around.
It's okay for a toy OS, but then please don't begin to refer to iOS as anything more than that.
It is NOT a reasonable OS if you're looking to do maintenance on your machine and yes, that is a crucial part of any reasonable workstation.
I've been running OS X for years without starting anew and whilst there are often issues with it, I usually fix them manually rather than setting up the OS anew for many dozens of hours until everything's set up correctly again.
Some issues remain unfixed, but having tested against clean installs on the same machine I know they are indeed issues with OS X itself.
Quality Assurance has gone downhill and Apple is certainly escaping responsibility in many areas these days, for example the lack of Apple's Hardware Test tools for newer machines.
You can't even do hardware diagnostics on newer machines anymore without bearing lots of BS Apple is making you endure.
They stopped providing meaningful error codes just so you go to Apple to get your stuff fixed.
I know I just went off-topic going from software to hardware maintenance, but with Apple the kind of **** that's happening it's very much fueled by the same OVERLY secretive and destructive philosophy.
Glassed Silver:mac
To assume a more complex OS should be at the same stage as one from 2013 is a bit of over simplification. iOS today is far more complicated than iOS6. It has to handle many more devices. It's not as simple as "at 6 months it should be good."
I cannot use my Safari at all because every link is non responsive. I have the iPhone 6S 128GB 9.3 IOS with Booking app as well. How does this happen with so many betas and tests done before the release?
Very witty. But this has been reported as a bug on the beta versions for weeks. Magic not required. Just a standard beta testing process.
Because iOS 9.3 introduced too many new features at once and the hyped Beta Program was inadequate.
iOS 9.3 was a rush job, and stuff like this shows it.
It doesn't seem to be related to the release, so the betas don't really apply one way or another.
And there's that point again. If you're going to use that logic, I hope you don't agree with this statement:
How is it that iPhone OS 2 is considered less complete and stable than the more complicated iOS 6?
It's not as simple as "at 6 months it should be good". Personally, I'm all for "it should be good as early as possible" and over 6 months is a little obscene to fix an already existing software product.
Software like Windows XP is five times more code than Windows 95, but it didn't take five times as long for them to make XP because of that. The software becomes more complex and developers become more skilled (or at least they should, and evidently have not at Apple) as those advancements go on.
Not witty, but realistic. And where has this been reported as an issue in betas for weeks? This affects iOS 9 versions prior to iOS 9.3 as well, so it's not even beta or release related, so nothing really standard about it.
If it takes that long to verify whether features actually work, Apple should slow its roll and not jam a bunch of unreliable, insufficiently tested features into a Beta, just to meet a release date. Night Shift could have been in 9.3.1... but oh no, it had to be in 9.3... and that explains everything.
With one of the longer beta cycles with pretty much the most betas released compared to most other versions it hardly seems that things were rushed.
That said, given that the links issue affects versions of iOS 9 prior to iOS 9.3, all of this iOS 9.3 beta discussions are rather moot.
