Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Oh just another things Not mentioned (found it the same day I found the linksgate): also if you try to send a link to the reading list from another app it doesn't work (no freeze or crash, simply doesn't add the link to RL).
I use the reading list very often from the Reeder app or NewsFlash :mad: this can confirm the deep linking bug (the apps can't communicate between each other)

Now you mention it: I have noticed this too. I thought it might be a bug in the app I was using (Tweetbot) but this makes sense: send link didn't work on my iPad (which is affected by the link bug) but does work on my iPhone (which isn't affected).
 
Easy on jailbroken devices, already said...

Reply to your question: https://developer.apple.com/library/ios/documentation/Security/Reference/SharedWebCredentialsRef/

That's the point from the beginning:
wrong certificates. Apps can't verify itself or something like that (due to Apple problem, not apps, and not booking.com :D )

When the app is installed, the system downloads and verifies the site association file for each of its associated domains. If the verification is successful, the app is associated with the domain.

If you read through this thread, an app starts the issue on a device. Which is why it affects some phones and not others. https://twitter.com/paulpols/status/714496472272789504

booking.com app is only the first app found to start the issue. There are probably other apps to that will cause the phone to fail handling links. Apple did a poor job allowing for this link capability from being un-done when an app is deleted. I guess the fix may be multi parts for this issue.
 
Here's the only workaround at the moment: Turn off Javascript in the "Advanced" pane of your Settings for Safari
Just called the Apple Care, same useless suggestions (JavaScript + Bing + total reset without the backup). The only interesting thing they said (after I felt very irritated :D ) that the engineers are working on a new version of Safari WebKit engine (but I don't know if is an accurate information). That could also point to my previous post: on my iPhone with the WebKit update log I haven't the linksgate, on my iPad Mini 4 I haven't that log and I have the bug. Just suppositions :)
[doublepost=1459178097][/doublepost]Oh just another things Not mentioned (found it the same day I found the linksgate): also if you try to send a link to the reading list from another app it doesn't work (no freeze or crash, simply doesn't add the link to RL).
I use the reading list very often from the Reeder app or NewsFlash :mad: this can confirm the deep linking bug (the apps can't communicate between each other)

I have gotten the Javascript workaround to work as long as I change my search engine to Google (not too happy about that). I was hoping the update that came out today would fix this problem, but it does not. I'll stick with the workaround until they come up with a patch.
 
Here's the only workaround at the moment: Turn off Javascript in the "Advanced" pane of your Settings for Safari


I have gotten the Javascript workaround to work as long as I change my search engine to Google (not too happy about that). I was hoping the update that came out today would fix this problem, but it does not. I'll stick with the workaround until they come up with a patch.

That is a temp fix for safari only, links everywhere else will freeze.
 
Just FYI I had to reset all settings on my iphone this evening for a different reason. This does not fix the problem either.

You have to do a clean restore through itunes and not install whichever apps are causing this, for sure booking is one of them. Hopefully we can get a app list to avoid until apple releases a fix.
 
How does turning off JavaScript work better than switching your search engine to Bing?

I would stick with bing since some sites can be broken without javascript according to some of the posts I've read on here. You can also keep google just hold the refresh button and use the desktop version for now.
 
You have to do a clean restore through itunes and not install whichever apps are causing this, for sure booking is one of them. Hopefully we can get a app list to avoid until apple releases a fix.


I restored back to 9.2.1. Booking.com app is part of my restored backup. However I never had opened it when the problem started for me. 9.2.1 is working for me so far.

BTW I see there is booking.com app update today.
 
Here is a reply from the whatsapp team for my question regarding this,

This is an issue caused by the iOS and not WhatsApp itself. Unfortunately, there is nothing that we can do from our end to fix an issue with the iOS. Please contact Apple Support for additional assistance.
 
So, basically Apple won't suggest switching the search engine to Bing, and instead is offering a lesser solution that renders a lot of websites unusable?

BTW, I just updated my iPhone 5 to the latest 9.3 in the hope that they had snuck in a fix for this. Nope, they didn't.
 
I did another backup restore. It seems in the meanwhile booking.com was updated. I have opened all my applications and everything is still OK. I guess Apple might have worked with apps that were causing it. I guess resetting everything and then restoring from backup cleans up the messed up database. Hopefully with apps already fixed, the problem won't reappear and Apple will also update iOS to also fix their database handling.
 
I just chatted with Apple Support and they told me that they are going to release an update (fix) in the next few hours...

They seemed to be aware that it was due to the long links that take you to apps as opposed to just a web page. The most common one people have is Booking.com. That is the one that I had... It does not get fixed by simply removing the app and restarting.
 
  • Like
Reactions: shrtmkr
I did another backup restore. It seems in the meanwhile booking.com was updated. I have opened all my applications and everything is still OK. I guess Apple might have worked with apps that were causing it. I guess resetting everything and then restoring from backup cleans up the messed up database. Hopefully with apps already fixed, the problem won't reappear and Apple will also update iOS to also fix their database handling.

What version is the updated app?

EDIT: nvm it finally showed up on the app store its 11.3.2
 
So, basically Apple won't suggest switching the search engine to Bing, and instead is offering a lesser solution that renders a lot of websites unusable?

BTW, I just updated my iPhone 5 to the latest 9.3 in the hope that they had snuck in a fix for this. Nope, they didn't.
Basically neither of the solutions often end up working for many people--sometimes one or the other might, with the JavaScript solution seemingly being more likely to do it, but far from always, and sometimes even for those that it works it stops working a bit down the line. There haven't really been any fixes to the issue from Apple just yet.
 
I just chatted with Apple Support and they told me that they are going to release an update (fix) in the next few hours...

They seemed to be aware that it was due to the long links that take you to apps as opposed to just a web page. The most common one people have is Booking.com. That is the one that I had... It does not get fixed by simply removing the app and restarting.

Next few hours? Really? After re-releasing 9.3 today that seems odd. Would be good if true. My thoughts are tomorrow or Thursday.
 
Apple support is saying delete 9.3 and redownload today's build.... I'm skeptical but I might try this. They say it fixes both the activation issue AND safari....
 

Attachments

  • Screen Shot 2016-03-28 at 1.10.37 PM.png
    Screen Shot 2016-03-28 at 1.10.37 PM.png
    127.1 KB · Views: 243
Apple support is saying delete 9.3 and redownload today's build.... I'm skeptical but I might try this. They say it fixes both the activation issue AND safari....
How would that resolve the issue for all those people with iPhone 6 and later and iPad Air 2 and later given that the new iOS 9.3 build wasn't released for them (since it was only released to address the activation issues for older devices)? As is often the case, unfortunately, it seems like not everyone that is providing support should really be providing it, unfortunately.
 
Next few hours? Really? After re-releasing 9.3 today that seems odd. Would be good if true. My thoughts are tomorrow or Thursday.
Unless it's somehow some sort of a backend fix/change and/or something else other than an actual iOS update. Doesn't sound likely, but who really knows at this point.
[doublepost=1459196206][/doublepost]
What is 233 and 234?
Build numbers (or basically the last few digits of build numbers) of iOS 9.3 for various newer devices, like iPhone 6 and 6s line of phones, which didn't get new iOS 9.3 builds today (at least certainly not so far).
 
  • Like
Reactions: DaveChappers
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.