I never knew how much links defined my life till they were gone. They are back now. They blame everything on the Booking app, but I don't have that installed on my iPad Air 1. What gets me is that if it wasn't for Macrumors, I wouldn't have known this was a widespread bug and not just a problem in my iPad. I also wouldn't have known about the fix if it wasn't for this site - the software update notifier was showing anything. Thanks guys - I'm very grateful.
To me, it feels a bit linkier.The one update where Safari actually feels snappier.
I want a public statement from Tim/Craig to all customers that they are changing their iOS development process to prevent errors like this in the future, whether it's from iOS or the Apps.
For now....The one update where Safari actually feels snappier.
Yes, we've been over this. This issue was present in iOS versions prior to iOS 9.3, so anything related to 9.3 and its beta process that gets referenced is basically moot as it doesn't have any relation to it.We've been over this. Apple needs to freeze all development on new features for a year and assign its team to improve the quality of the existing feature set.
That's real world. That's not utopian. That's called reliability and fault testing.
So, here's a realistic scenario: something was reported to Apple in very low numbers, Apple started investigating and aside from not seeing many people affected, they also noticed the issue affects versions prior to iOS 9.3, and all along continued figuring out more details about it and looking for what the best way to fix it would be--releasing or not releasing 9.3 would have no effect on whether this bug would become an issue given that previous versions that were already out there that people were already on were already susceptible. So, again, the release of 9.3 is moot in this discussion.See here: https://forums.macrumors.com/thread...s-crashing-issue.1964477/page-9#post-22739147
It was reported to Apple, and they shipped 9.3 anyway.
And that is certainly a very realistic scenario.Could be correct. I never saw a mention of this being reported during the betas but I find it interesting that 9.3.1 web traffic was spotted a while back and today that's the only item listed in the change log. So perhaps it was not ready and still being tested not ignored.
It wouldn't have mattered if there were 100 betas, this issue was NOT present in the betas. They must of changed something between the last beta and the GM. Apple acknowledged there was an issue and released a patch. On Android, you'd be waiting months for a fix...
How about Battery Life issue and auto brightness which is not working correctly so this minor update doesn't fix other issues with iOS 9.3, strange that this went multiple beta testing and still they create problems.
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 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.
Never seen anything like that on "Android" so who might know where the truth is...On Android, you'd be waiting months for a fix...
The bug was already there in previous iOS releases that were already out in public before the latest release.Reproduction steps is the path to addressing/fixing the bug. But does not speak to awareness that the problem exists. If they chose to release a software update out to the general public, knowing that a bug of such significance exists in the update... that seems very irresponsible. Could they not have chosen to wait before releasing the update, while they tried to figure out the problem? As a user affected by the problem... i 100% would have preferred to stay on the older version of software than update and have the bug.
Just like not everyone by far has experienced the issue in this update or even heard of it, which can mean that it probably doesn't exist, right?Never seen anything like that on "Android" so who might know where the truth is...
Yeah, it's the whole Universal Links thing: http://www.wired.com/2016/03/apple-...recall-the-bad-old-days-of-internet-explorer/It was caused by some Einstein at the Booking.com dev team who crawled their website and setup universal links to each individual URL -- think every hotel in the world. Apparently, the concept of pattern matching hasn't arrived in Amsterdam yet. (Side note: WTF, who was going to maintain that list?!?)
So the association file that should've been a few KB, tops, was 2.3mb, which was far more than the link process was built to digest. It was even too large to be fixed naturally during an uninstall. iOS 9.3.1 addresses those issues, and hopefully someone on the Booking.com dev team is learning to do code reviews.
As to the question, "Why the eff would we want every URL clicked to be preprocessed?" What, so app devs can hijack Safari and load their app instead? Only knows for sure...
I'm only saying that, to my limited knowledge, I'm not aware of an issue like this one happening on Android phones (maybe given the fragmentation...) so nobody (as far as I am concerned) can be sure about the time it would have been necessary for a fix.The bug was already there in previous iOS releases that were already out in public before the latest release.
[doublepost=1459450032][/doublepost]
Just like not everyone by far has experienced the issue in this update or even heard of it, which can mean that it probably doesn't exist, right?
The easy solution to your particular wishes is for YOU to not update for a year. If 9.3.1 fixes your issues and you can click links now (which is apparently all you use your device for) then wait it out and don't update every year. In summer of 2017, you can review how well iOS 10.3.2 is working for others and update then. Problem solved!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.
And that probably still might not necessarily escape some deeper bugs that might surface down the line and are present going back some versions.The easy solution to your particular wishes is for YOU to not update for a year. If 9.3.1 fixes your issues and you can click links now (which is apparently all you use your device for) then wait it out and don't update every year. In summer of 2017, you can review how well iOS 10.3.2 is working for others and update then. Problem solved!
It's still an Apple problem. The tools were broken. A screwdriver can be used improperly, but it's not much use if it's made from rubber.It was caused by some Einstein at the Booking.com dev team who crawled their website and setup universal links to each individual URL -- think every hotel in the world. Apparently, the concept of pattern matching hasn't arrived in Amsterdam yet. (Side note: WTF, who was going to maintain that list?!?)
So the association file that should've been a few KB, tops, was 2.3mb, which was far more than the link process was built to digest. It was even too large to be fixed naturally during an uninstall. iOS 9.3.1 addresses those issues, and hopefully someone on the Booking.com dev team is learning to do code reviews.
As to the question, "Why the eff would we want every URL clicked to be preprocessed?" What, so app devs can hijack Safari and load their app instead? Only knows for sure...
The easy solution to your particular wishes is for YOU to not update for a year. If 9.3.1 fixes your issues and you can click links now (which is apparently all you use your device for) then wait it out and don't update every year. In summer of 2017, you can review how well iOS 10.3.2 is working for others and update then. Problem solved!