OK, so users with a particular
app had Safari issues, the app got patched, and Apple's planning on fixing their end of the bug per
http://techcrunch.com/2016/03/28/its-not-just-you-clicking-o.... "Booking.com associates its app with all sorts of domains — too many domains to be precise. With 2.4MB worth of domain-name-to-deep-link entries, Safari and other apps crash when iOS checks links against its Universal Link database because this database is too big."
Your criticism seems doubly odd now. Should Apple pause all Safari development whenever a bug is encountered? What are you proposing?
edit: Since I can't reply:
> Any app with a link association file that had too many links can cause Safari to totally stop working.
Yes, there's apparently a bug, triggered by the rare apps that pad out the file to enormous sizes. Not sure why you felt the need to spend ten minutes updating your post with every mention of it you could find (along with unrelated stuff from 2015).
> This has been discussed to death already, you are very late to the party here.
I'm extremely sorry I missed a bit of tech news about an edge-case bug that doesn't affect me. I'll try harder in the future.
> It's totally within the realms of possibility that Apple can do more frequent bug fixes and develop new features.
OK, but from the looks of the dates on those articles, this bug has been known about for about a week. Do you always fix every reported bug in a week or less, or do they sometimes take a little while to fix and QA? iOS has a bit of a larger user footprint to consider, too. Given there's a workaround - patch the apps with bloated link associations - I'm dubious of the need to rush an update here.
edit 2:
> edit: you can reply, press the link that takes you to my direct comme t and hit reply.
No, I can't. "Submitting too quickly".