iOS 10 Carrier Updates Causing Issues for T-Mobile Users in U.S., Telstra Users in Australia

That's why I have att :p

Now who's to blame here?

Apple is probably already "investigating". As usual. Something they prefer over testing prior to rollout.

T-Mobile is to blame.

Of all the things on an iPhone, the only part that Apple doesn't have control of is the carrier. If T-Mobile pushes out bad settings and there's something wrong with them, that's no more Apple's fault than an app in the app store being buggy. Less than even most there, in fact, since the bug only appears when interacting with an external piece of hardware (the cell tower), at that.

That said, it certainly isn't everyone--I'm on T-Mobile and both of the phones in my house seem fine.

A Telstra employee replied ('http://whrl.pl/ReIo1X') in that Whirlpool thread, confirming they are aware of it, and it's not limited to iOS 10.

Just a update – we've narrowed the issue down and it is not specific to iOS 10, we've found it on users with iOS 9 as well. Still working to address it.

Finally acknowledged by T-Mobile, fix on the way...

https://twitter.com/TMobile/status/776466023193030657

This is happening to me. It won't automatically reconnect to the network after losing signal. I also updated through iTunes. I'm hoping T-Mobile rectifies this soon. I don't want to have to revert to 9.3.5.

Reverting to 9.3.5 will not resolve it. Its a carrier update not iOS.

Now who's to blame here?

Apple is probably already "investigating". As usual. Something they prefer over testing prior to rollout.

And they will claim that only a tiny insignificant amount of users were affected. As usual.

Carrier update not Apple update. It's T-mobile's burden to fix.

Randomly happened to me yesterday. Just totally lost cellular connectivity. It came back on after a phone call though.

Did you stop to think that iOS10 may not be handling new carrier settings correctly? Not sure if any other carrier has pushed new settings since iOS10 or if T-Mobile is the first to do so. But please, continue with your absolute statement.

It's certainly possible, but seems unlikely, since it would mean that iOS10 was able to read and apply the new carrier settings, but somehow goofed them up during installation such that they still function but have bugs.

More to the point, I would hope that T-Mobile actually tests new carrier setting rollout before making them live, so even if that were true I would expect them to have caught this and reported it to Apple while testing these new setting pushed out to iOS10 during the GM period, and held off making it live to everyone in their customer base until the bug was fixed.

It doesn't matter whether the actual bug is in iOS or the settings, T-Mobile is responsible for making sure those settings are going to work with whatever OSes they're pushing them to.

Now, maybe I'm wrong and Apple doesn't let major carriers test OTA settings rollout until they're pushing them live to several million customers, but that would kind of surprise me.

Or maybe they don't let carriers test OTA settings rollout on beta OSes, but in that case I don't see why T-Mobile wouldn't have waited until the OS was released and they could test it properly before pushing it to all customers.

Or, heck, maybe the carrier settings are entirely done in-house by Apple. That would make it Apple's fault, not T-Mobile's, although again, it would surprise me.

And I say this as a T-Mobile customer. If it's an uncommon bug maybe they just didn't stumble upon whatever combination of local and cell tower hardware and software triggers it, and I'm not going to get too worked up if they resolve it quickly, but it's their responsibility to make sure it works.

[Edit: Although T-Mobile seems to be claiming that the problem is universally with iOS10 and has nothing to do with the carrier update, which would be a different situation. Still a weird situation, though--why wouldn't they have caught this bug with the GM unless it's extremely rare, and why would Telstra be claiming that it's universally a problem with the settings, not the OS, unless their problem is completely different and just has coincidental timing?]

Now who's to blame here?

Apple is probably already "investigating". As usual. Something they prefer over testing prior to rollout.

And they will claim that only a tiny insignificant amount of users were affected. As usual.

Many issues usually do only affect a small amount of users, but either way- it's all Apple's fault. Because everything bad that's ever happened anywhere is Apple's fault.

T-Mobile definitely affected - have major issues even texting, hugely disappointed.

Really? My service is working just fine, wonder if it's area thing?