Come on, Apple. This is the kind of crap you should detect with your QC! If people didn't have this issue with the beta, then there's no reason they should have the issue now.
OOPS ... they did it again.
The Apple PR group will be along shortly to downplay this incident.
I rarely bash Apple but wow. What the hell is worng with their QA these days?
Well, T-Mobile sucks so no surprise there.
Why would it be Apple's fault? Seems like a network issue for T-MoI rarely bash Apple but wow. What the hell is worng with their QA these days?
Come on, Apple. This is the kind of crap you should detect with your QC! If people didn't have this issue with the beta, then there's no reason they should have the issue now.
Sorry Apple and T-Mobile both said it was iOS 10.
If this is still the "quality" of pre-testing Apple have now, I will stay well away from Sierra for some while!
Hey Apple! I know you release each new Beta out to the General Public to try & get as wide a possible testbed, but do you realise many of these "testers" are just kids who "have to have" the latest OS, but don't really "test" it, thus few negative responses?
OOPS ... they did it again.
The Apple PR group will be along shortly to downplay this incident.
I don't think Apple tests Carrier updates or at least makes the carriers push betas out. This issue specifically happened after T-Mobile's 25.1 update and it also affected some iOS 9.3.5 devices.I rarely bash Apple but wow. What the hell is worng with their QA these days?
I don't think Apple tests Carrier updates or at least makes the carriers push betas out. This issue specifically happened after T-Mobile's 25.1 update and it also affected some iOS 9.3.5 devices.
But you know, go ahead with the Apple Hate and whining
But you know, go ahead with the Apple Hate and whining
Hmm. Then why is it stated that the fix will be released by Apple - not T-Mobile - if it is purely a T-Mobile fault?I don't think Apple tests Carrier updates or at least makes the carriers push betas out. This issue specifically happened after T-Mobile's 25.1 update and it also affected some iOS 9.3.5 devices.
But you know, go ahead with the Apple Hate and whining
Exactly, Why wouldn't it have shown up during beta even GM week? I find it hard to believe no T-Moblie users were using the GM prior to Tuesday. Something weird here.It seems like this would be something related to the carrier settings and a carrier settings update should be able to fix it.
Maybe so but how do you NOT test a failed cellular signal? Just curious?If this is still the "quality" of pre-testing Apple have now, I will stay well away from Sierra for some while!
Hey Apple! I know you release each new Beta out to the General Public to try & get as wide a possible testbed, but do you realise many of these "testers" are just kids who "have to have" the latest OS, but don't really "test" it, thus few negative responses?
Free international text and data, and unlimited talk/text/data in the US on two lines for less than $100/month? I'm not complaining.
If you don't tell Apple, and just restart?Exactly, Why wouldn't it have shown up during beta even GM week? I find it hard to believe no T-Moblie users were using the GM prior to Tuesday. Something weird here.
[doublepost=1473967590][/doublepost]
Maybe so but how do you NOT test a failed cellular signal? Just curious?
There will always be permutations of the hardware and software mix that the Beta testers did not know about. It could be a rare unique set of applications running that the testers did not have.This didn't come up during the beta testing?