Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Quit being dramatic. It seems to be limited to people using the booking.com app or perhaps a small subset of apps, but it's clearly not that widespread. That's not a "huge number" and the devices are not "useless." Why do you insist on exaggerating so much? Remember that video a while back where the woman didn't have an appointment at the genius bar and lost it, screaming about her outrage and trying to make a scene and ended up looking like a weirdo? Yeah, that.
To be fair given how large the thread about this at https://forums.macrumors.com/threads/ios-9-3-links-in-safari-not-clickable-anymore.1962471/ has gotten and how quickly it got there it's fair to say that it's likely more than a minor issue at this point.
[doublepost=1459172207][/doublepost]
Because most people want to cry about issues that aren't even there most of the time
Doesn't seem to apply in this case (unlike some other cases where people try to come up with non-existent issues about the SE, for example).
 
Issue seems to be happening more often with Peek&Pop... I have not had the issue on my iPhone 6S Plus when using safari without 3D Touch.

Peek and Pop rely heavily on the routing system which is the component that is failing, so that makes sense.
 
  • Like
Reactions: dysamoria
Peek and Pop rely heavily on the routing system which is the component that is failing, so that makes sense.

No problems using peek and pop on the favorites sheet in Safari (but all other link issues exist on my iPhone). iPhone 6S+ 128GB 9.3.
 
To be fair given how large the thread about this at https://forums.macrumors.com/threads/ios-9-3-links-in-safari-not-clickable-anymore.1962471/ has gotten and how quickly it got there it's fair to say that it's likely more than a minor issue at this point.
[doublepost=1459172207][/doublepost]
Doesn't seem to apply in this case (unlike some other cases where people try to come up with non-existent issues about the SE, for example).

Very clever i see what you did there :rolleyes:
 
If I'm honest I can never understand this.

If this was Windows, and Microsoft had to, which they do, make things work on millions of not billions of permutations of hardware, built from anyone from a giant company, down to a child in his bedroom from second hand bits, then sure, we'd all expect things like this.

But when YOU build the hardware yourself, and there are such a tiny number of variations out there, it always amazes me, how, even after multiple beta's you can have things like this happen.

Apple have it so easy.
You don't understand API and app development. That causes billions of possible failure points because of how many different ways the system can now be used. You cannot test them all.

I'm convinced Apple doesn't do any user testing outside their bubble of an office.
They have a rather good feedback app for testers. It takes just a few minutes to submit a bug report. I'd say 75% of the over 30 I've submitted for iOS 9.x have been fixed. The ones that haven't are generally enhancements I'd like to see and not bugs. You're lucky you haven't seen some of the bugs that were there.
 
This was related to the deep linking process that allows you to move from a page on the website to the associated view in an app and vice versa, and other various routing for apps. This wasn't caused necessarily by the app, but a system process that was impacted by the legit, but naive use of a set of APIs, by another app.

They were pairing a lot of data and it seems like no one has ever added that amount before - nor was it intended to have been used in that fashion. The iOS process should have been able to preemptively anticipate the situation or just be able to do it, but because of a bug or unexpected result, the process was thrown into an unstable state.

Not only do apps do weird things in unexpected states, a system process like that spans lower than apps meaning its failure to work in the Bookings app made it unstable when handling routes for the Quora app. Thus, either Quora would get invalid information and crash because it should have never gotten that result, or iOS itself would respond to the garbled data and kill Quora on its own.

That's a basic overview without any real deep searching of information, but generally that's how things like this work.

Makes sense. Thanks for taking the time to help us unenlightened ones out.
 
God damn it! How on Earth can this happen after so many betas and on a system so closely guarded and in house custom made. It practically broke both my iPhone 6s and iPad Air 2. Absurd that **** like this happens with the prices they are charging for their Made in China crap=hate to say it, but this is what Apple has become.
 
Apple has a billion active devices. The vast majority have no problem. Until there are a billion angry users, sorry, but a list of random tweets don't mean anything. Saying "oh look at this thread" is the new "______ 'broke the internet.'"
ok, no problems going on. What a surprise, I knew it the very moment I answered your post.
Bye then.
 
Apple has a billion active devices. The vast majority have no problem. Until there are a billion angry users, sorry, but a list of random tweets don't mean anything. Saying "oh look at this thread" is the new "______ 'broke the internet.'"
It's fair to say that many people didn't run into activation issues related to iOS 9.3, yet Apple commented on it and pulled the update for some and released and update for some as well.
 
God damn it! How on Earth can this happen after so many betas and on a system so closely guarded and in house custom made. It practically broke both my iPhone 6s and iPad Air 2. Absurd that **** like this happens with the prices they are charging for their Made in China crap=hate to say it, but this is what Apple has become.

Either it wasn't IN the beta (more than likely) or the beta group was such a small number compared to the millions of people who installed 9.3, the problem was not seen until then. It happens. Enjoy all your China made crap. :)
[doublepost=1459173553][/doublepost]
ok, no problems going on. What a surprise, I knew it the very moment I answered your post.
Bye then.

Bye Felicia!
 
Personally, I would love, love, LOVE for iOS 10 to be a Snow Leopard kind of release. But I would imagine there is far too much temptation and expectation to do something "big" for the number 10. And think about it... remember the days when these forums were filled with the same huge lists of feature requests that Apple seemingly refused to deliver on year after year? You don't see very much of that anymore. I know Apple is always looking for ways to make iOS stand out, but if you can (generally) satisfy the kind of people that frequent MacRumors in regards to feature requests, I'd say you can relax for a bit and focus on performance and GUI issues. iOS is great, but it could be so much better with more polish.

lol, that was already the goal for iOS 9: http://www.theverge.com/2015/2/9/8005669/apple-ios-9-stability-bug-fixes
At this rate, every release is gonig to have to be a "Snow Leopard-like" release.
 
  • Like
Reactions: dysamoria
I remember a time when OS releases were stable, under Scott Forstall of course. Everything from hardware to software is just flimsy now.

This report does not even start to address the number of times Safari says, "site error, must reload" or some such, or the often recurring "you are not connected to the internet", but I most certainly am. When I really need to do something, it is often that I can't use Safari.
 
  • Like
Reactions: Benjamin Frost
I'm so damn sick of every public release of iOS feeling like a beta. And right around the time things start smoothing out after multiple .X updates we get the next full iOS release and start all over. It's not like it's unusable but this is the norm nowadays. Oh, and then the exceptionally feasible and reasonable option to restore as new each time... I love that one. </bitching>

Apple now days is all about the big show. Now don't get me wrong, Steve J loved a big show, its just that he demanded that things were pretty right (maybe not perfect) for the show and no one wanted to let him down. Apple's leadership today, evidently does not mind being let down. These things keep happening and no one seems to care.
 
  • Like
Reactions: Benjamin Frost
If I'm honest I can never understand this.

If this was Windows, and Microsoft had to, which they do, make things work on millions of not billions of permutations of hardware, built from anyone from a giant company, down to a child in his bedroom from second hand bits, then sure, we'd all expect things like this.

But when YOU build the hardware yourself, and there are such a tiny number of variations out there, it always amazes me, how, even after multiple beta's you can have things like this happen.

Apple have it so easy.

Software has bugs. The sky is blue. The grass is green.

Even if you're in control of everything, bugs still present themselves. Thinking that controlling your platform gets rid of bugs is ridiculous, yet your comment is the most upvoted.

Oh, people.
 
  • Like
Reactions: TheHorrorNerd
question from a non-developer: how can a sandboxed app have such a huge impact on Safari and the OS in general?

Sandboxing prevents unexpected data from getting out. What it doesn't do is stop an app from triggering OS bugs because they provide data that is valid, but creates bad states in the OS. The OS here is doing two things: reading this information on what URLs an app opens, and then caching it in a central database to make lookups faster. If there's an Apple bug there, then not only will this valid data cause problems, but also iOS may cache the data and still keep trying to load it from the cache, continuing to crash.
 
  • Like
Reactions: dysamoria
lol, that was already the goal for iOS 9: http://www.theverge.com/2015/2/9/8005669/apple-ios-9-stability-bug-fixes
At this rate, every release is gonig to have to be a "Snow Leopard-like" release.
That was indeed the goal of iOS 9. Safari is noticeably more stable under iOS 9 and some bizarre crashes in other apps were fixed, but performance and UI issues either stayed the same or regressed depending on who you talk to.

Even if we never get a true stability and performance-only update, I think the best course of action at this point is to make specific concerns known via the Apple Support Twitter account. If enough people make their voices heard, I think we could see some real improvements on that front.
 
I wish Apple would have simply provided a switch to disable the "deep link" functionality. In general, I find it useless, and in most cases want to keep browsing in Safari rather than jump to a 3rd party app. Perhaps now Apple will decide to give us control over this feature now that it's been shown to be able to kill Safari functionality when deep linking goes wrong.

Ideally I'd like this control app by app and I'd still like the ability to override it on a case by case basis. For example, I search a business name in safari and click on a link that happens to be to yelp, I don't want the yelp app to auto-launch every time that happens but there may be an occasion when I do (e.g. I want to order food or make a reservation). Give me something like the "there's an app for that" panel that shows up at the top of some websites (not a pop up dialog please) giving me the option to hand off to the app. Maybe even make that prompt configurable so for some apps I never have to see it (e.g. LinkedIn I would never want to redirect). On the other hand, Open Table would be an app I always want to launch (I'd never go to their web site other than to book a table so may well put me right into the app) so configuring it to redirect automatically would be my preference.

In other words I think this idea and then some.
 
  • Like
Reactions: chrfr
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.