How so? What's this horrible experience you speak of? Even if it was, how is that any type of consolation for anyone with an Apple device?It's a rock solid experience compared to Android. Go on then, off you pop...
How so? What's this horrible experience you speak of? Even if it was, how is that any type of consolation for anyone with an Apple device?It's a rock solid experience compared to Android. Go on then, off you pop...
Thank you. There are a bunch of people commenting on the "quality control problems" at Apple when it comes to software who really should just shut the eff up. They have no idea that:
A. Bugs are going to happen no matter how much testing occurs before release.
B. This is likely a small bug that affects relatively few of the approx. 1 Billion users out there. And if they weren't watching MacRumors like a hawk they likely would not have even known it exists.
There are over 1.5 million apps available on the app store, and any one of them can cause a problem with the OS, no matter how thoroughly it was tested.
And who says something like that won't be happening?
Again, thank you. No software is bug-free. I mentioned above, how were Apple to know that this Booking app could cause an issue? What do they need to do? Download every app and make sure iOS still works? I don't think so. And as you say, the users affected is probably like 0.0000002%.
And okay, the following was when iOS 9.3 was in the beta phase but the app Real Racing 3 wasn't working and people were complaining that Apple should fix it, it was ridiculous.
Did you not read the article? There's no correlation between not having the booking.com app and not being affected. It's right in the article.The Booking app seems to be the cause of the issue so how on earth out of the trillion of apps available were Apple to know that Safari wouldn't work? I don't have the Booking app and Safari has been working perfectly for me.
Wait for 9.3.1... Are they serious? I haven't been able to use Safari on my iPhone 6s going on 4 days now. This is completely unacceptable. It's a shame that Apple software quality has fallen so much.
9.3.1 should be a quick fix for this issue. 9.3.2 needs to be slowed way down and tested much more thoroughly for any issues.
What device? And have you tried some basic troubleshooting like clearing safari web data (cache) and turning off javascript? Also I wouldn't say that being unable to click a link in another page to get to the next site is "mission critical". Perhaps you should restore back to iOS 9.2.1 before they stop signing it. I mean if this only started when you updated to 9.3.I updated my post: The freezing issue is the most urgent fix, and I don't want it appended to Apple's planned 9.3.1 coming in who knows when. I want the fix for this freezing issued today as 9.3.1.
9.3.2 needs to be a feature locked and thoroughly vetted update that 9.3.1 was originally going to be, and not rushed out the door in order to provide a fix for the freezing issue.
[doublepost=1459281685][/doublepost]
See what?
Did you not read the article? There's no correlation between not having the booking.com app and not being affected. It's right in the article.
What device? And have you tried some basic troubleshooting like clearing safari web data (cache) and turning off javascript? Also I wouldn't say that being unable to click a link in another page to get to the next site is "mission critical". Perhaps you should restore back to iOS 9.2.1 before they stop signing it. I mean if this only started when you updated to 9.3.
The article is wrong - this only affects users with the Booking.com app (I had it on one of my devices affected, but luckily not the phone). Here is more detail on the bug: http://arstechnica.com/apple/2016/0...hes-and-link-problems-for-some-ios-9-x-users/Did you not read the article? There's no correlation between not having the booking.com app and not being affected. It's right in the article.
The complainers swarm on articles like these. We'll probably hear next how the iPod's click wheel sucks/sucked.OK, so far:
1. Apple sucks.
2. Apple software sucks.
3. iOS sucks.
4. The headline sucks.
5. iPhone sucks.
6. The accompanying chart sucks (no Y axis).
7. iOS Control Center sucks.
8. ???
This is why I didn't update. If it works, I leave it alone until I'm sure the next version works.
How so? What's this horrible experience you speak of? Even if it was, how is that any type of consolation for anyone with an Apple device?
Did you not read the article? There's no correlation between not having the booking.com app and not being affected. It's right in the article.
The complainers swarm on articles like these. We'll probably hear next how the iPod's click wheel sucks/sucked.
This issue isn't related to iOS 9.3. Most of what you are talking about seems to be more related to https://www.macrumors.com/2016/03/28/apple-releases-updated-ios-9-3/.The 9.3 update has been utter crap. On my 5s the original 9.3 update worked fine, but now it is nagging me to perform ANOTHER 9.3 update for no apparent reason. And when I select "Remind me Later" it pops up a screen asking me to enter my lock code so that it can install the update automatically overnight.
On the other hand, my wife and daughter both tried to install the update on their 5c phones, and in each case got the "device is not connected to the internet" error when entering their iCloud passwords. And their phones most certainly were connected to the internet.
So in some cases it won't install, in other cases it keeps insisting on reinstalling, and for other people apparently it bricks their devices. What a lousy, lousy update.
This doesn't really have anything to do with iOS 9.3.This is why I didn't update. If it works, I leave it alone until I'm sure the next version works.
It's not only related to that app as people even without that app have been affected as well.The article is wrong - this only affects users with the Booking.com app (I had it on one of my devices affected, but luckily not the phone). Here is more detail on the bug: http://arstechnica.com/apple/2016/0...hes-and-link-problems-for-some-ios-9-x-users/
Seems like the context there was related to things that are outside of what seem to be legitimate issues.Why are you dismissing people having legitimate issues on their iOS devices as "complainers"?
I have the same frustrations, but as long as apple has been writing code, code has become exponentially more complex than it ever was.Why? Writing code isn't new---Apples been doing it for a very long time. My issue is that these types of problems are becoming the norm vs. the exception. This release has been in beta for months yet we first see a bad version on 9.3 for older devices and now this.
Apple's reputation for polished software is getting a bit tarnished in my opinion.
I have the same frustrations, but as long as apple has been writing code, code has become exponentially more complex than it ever was.
Video games are a good case in point- The biggest and most popular game titles are riddled with bugs and glitches, so many it's a joke, but the software is designed to do so damn many things at once that there's little they can to to address them all. You're comparing Tetris to Halo.
sucks to be apple, right now. They are having a bad week!
I want what you want, but reality is what it is.I don't want new iOS features. I want Apple to put a freeze on all new iOS features for a year and focus on reliability. The only updates I want are bug fixes for known/unknown issues.
Legitimate issues aren't being dismissed. Why are you classifying my comment as such? IMO it's unfortunate that these articles turn into... "Let's complain about everything Apple" and "Apple sucks more and more" in stead of just discussing this specific issue. Complainers will complain because its a habitual behavior.Why are you dismissing people having legitimate issues on their iOS devices as "complainers"?