-
All replies
-
Helpful answers
-
Mar 30, 2016 8:31 AM in response to Agathornby dizzychoonz,i have installed the google search app ( not chrome) and this has allowed me to continue browsing..
but hasnt got rid of the problem on chrome/firefox/safari/
it is a temporary get around for me.. worth a shot
-
Mar 30, 2016 8:33 AM in response to DanielR1983by deggie,And I'm with 3 people who don't have booking.com and don't have the issue. Yes, it is more complex than people think it is.
-
Mar 30, 2016 8:38 AM in response to deggieby DanielR1983,Just because you are with 3 people who don't have the app and don't have the issues doesn't mean the app is the issue. Look at many other forums (just use google). Also, my dad on his iPhone 6 Plus has had the app installed since the release of the iPhone 6S Plus. My 6S Plus had the bug, his still does not and never got it despite both of us upgrading to iOS 9.3 at the same time. You'd have to be very foolish to ignore all the other facts (no offense).
-
Mar 30, 2016 8:43 AM in response to DanielR1983by Rosyna,It was previously explained to you precisely why the difference exists on those devices. Please don't ignore those facts while asking others to not ignore fact.
-
Mar 30, 2016 8:45 AM in response to DanielR1983by deggie,No offense but I didn't intend to provide any proof either way about the app. Just that it it a complex situation and the app may be involved in some cases or may not. The more information Apple can pick up from users with issues the faster they can come up with a sound approach.
-
Mar 30, 2016 8:45 AM in response to deggieby Rosyna,it is possible that if you have a very large number of installed apps that this can cause the swcd to crash in a loop as well due to resource size limits. Booking.com just happened to have a single association file that brought swcd past the limit, killing the ability to pass links between apps.
-
Mar 30, 2016 9:01 AM in response to Rosynaby DanielR1983,I will agree with the large number of apps theory, but cannot accept your explanation for why my dads 6 Plus never got the bug while my 6S plus got it yet both of us had the booking.com app installed & used the same iOS versions. I believe to be techhnically inclined enough to discern accurately what else may be clauding this issue. That being said, I work with developers and test apps on my iPhone 6S Plus and my Apple Watch while providing feedback on bugs. Personally I have over 400 apps installed, while my dad had about 50 on his iPhone, so for that reason your statement makes sense. Although I repaired my 6S Plus, I'm still very inquisitive and would like to follow the trail to the end to see exactly what created this mess to begin with. Knowledge is power.
-
Mar 30, 2016 9:07 AM in response to DanielR1983by Rosyna,As I mentioned previously, the bad file was only on Booking.com's server for about a week. iOS does not immediately update association files. If iOS did not download the updated file during that week, you would never see the problem.
This is also why testing updates to the association file is nigh impossible, there's no way to force iOS to download the update.
-
Mar 30, 2016 9:21 AM in response to Rosynaby DanielR1983,Shouldn't Apple have separate serves for beta testing current and future iOS versions as well as association files before pushing them through to a 'stable' platform? If you are correct, seems they have some time consuming improvements to make.
-
Mar 30, 2016 9:26 AM in response to DanielR1983by Rosyna,Association files are not submitted to Apple. They're stored on the web server of the domains declared in the app. Developers can change them at any time. Useful for when you completely redesign your website structure. They are first downloaded when you install an app, if it doesn't already exist in swcd.
-
Mar 30, 2016 9:32 AM in response to Rosynaby DanielR1983,But iOS ultimately downloads the association file.. So why not have iOS Download and Test new association files on a separate server loop for testing before being pushed through to a stable platform; as a security measure.?. This way they can safely identify bad code and blacklist it before pushing it through? You'd think an Empire like Apple could do something like that in their sleep.
-
Mar 30, 2016 9:38 AM in response to DanielR1983by Rosyna,I'm not sure what you mean.
Apple has zero control over the association file.
iOS does validate association files after download. It makes sure their signature is correct and that they are valid JSON. The issue is that when swcd goes to store the processed file, it chokes if the database ends up being too big. That's the error that needs fixed in swcd.
-
Mar 30, 2016 9:43 AM in response to Agathornby Nicky195733,After update to iOS 9.3 on my iPhone links on both Google and within emails do not work. Have tried using DuckDuckGo as search engine on Safari with no change. Also only updated Booking.com this morning.
-
Mar 30, 2016 9:45 AM in response to Rosynaby DanielR1983,You said what I mean clearly in your 2nd sentence: Apple has zero control over the association file. That's where I believe Apple has made the biggest mistake; that is what needs changing. Yes, it'd slow things down but provide much more safety to the end user. Giving complete trust to every app developer to speed things up while compromising safety is undesired.
-
Mar 30, 2016 9:57 AM in response to DanielR1983by Rosyna,I Don't see how giving developers control is bad here. It's an extremely simple text file. The contents can't execute code or otherwise damage the system. (swcd crashing isn't due to the content, but the size of the processed output).
Even if Apple had control over association file approval, swcd would still crash from this bug if too many total entries exist (too many apps).