Same here, 4th day with dumb iphone.. awesome experienceThis is a joke, right? I'm going on Day 6 of my iPhone being unusable due to the links bug.
View attachment 624197
It's not a 9.3 bug, but a 9.x bug, it happened to people who had 9.2 also. It still sucks that it doesn't get fixed, though. Fortunately, this happens only on my iPad, not on my iPhone.This is a joke, right? I'm going on Day 6 of my iPhone being unusable due to the links bug.
Why do you consider the two to be incompatible?This is a joke, right? I'm going on Day 6 of my iPhone being unusable due to the links bug.
Over 80,000 people have visited the Apple support page on the hyperlink issue thread. This is a representation of only a portion of the people with the problem. Not everyone goes to the Apple support forums.
sshhh, don't say it again. Anyway numbers on Android latest are totally different and so a comparison would be biased from the startSo except 9.3, Android is more stable than iOS?![]()
Seriously? I don't see any big feature, let alone "great". Nighshift is nice, the rest is of little interest. Hopefully iOS 10 will offer much more relevant and impressive new features.Is it just me or will iOS 10 be a no-show at WWDC this year? I'd figure the features in 9.3 would've been great key features if they held them out for just a few more months.
It's very doubtful that there's a large number of looky-loos. The vast majority of the people don't go to the support page unless they have a problem. Yes, all agreed it will be a small amount that would go that don't have the problem, but we're still talking tens of thousands of people that have this issue. And these are only the ones that have gone to the support page for AppleDoesn't mean all those viewers are having an issue either. I am tempted to go to that page and check it out but I am not seeing any issues and am wondering if I am doing something wrong.
Now if we could just get Safari to recognize that it IS connected to the internet and that the web page IS valid and does not need to be reloaded, both of which make using it frustrating at least. So maybe 9.3 has the least crashes, but I would not say it was the most pleasing.
So where's the walled garden utility? One subject designs hardware and define specs. The same subject designs software and defines limits. The same subject define rules for ALL any other who may want to interfere. The same subjects set rules for providers, users (yes, you can't do whatever you want with your phone), developers etc.What a stupid comment. Apple has hundreds of millions of customers using iOS and it would be impossible to put out a version that works 100% for every single user. Even if only 1% of users are having a problem that's still millions of customers, but at the end of the day there's nothing you can do about that. Every device is unique, with different apps and services running, everyone uses their devices in different ways. That inevitably means that 101 things can and will go wrong. Apple patches what they can but it would be impossible to find out every single problem and push out a fix for it.
Fortunately I don't have any of these issues that people seem to be complaining about on the web, the same goes for the hundreds of millions of customers who aren't making a song and dance about it. The minority seem to shout the loudest and it amplifies. The figures speak for themselves, plus I seem to recall Craig Federighi saying recently that things have gotten better according to their own data. Just because one person has a problem and they feel entitled to have it fixed right there and then doesn't mean they speak for iOS and every user as a whole.
It's not a 9.3 bug, but a 9.x bug, it happened to people who had 9.2 also. It still sucks that it doesn't get fixed, though. Fortunately, this happens only on my iPad, not on my iPhone.
edit: I've told you again this in another thread.![]()
Thankfully, I think I'm one of the only people who hasn't had any problems with this release.
was about to reply with the same answer, even if you are still on 9.2 the booking app would have caused this issue.