Hi Lawrence - a few things:
If you think I spent that much time as I did (not an exaggeration) on the phone with support, on both sides, without speaking with senior support agents, you must think me a dim bulb indeed :) your information that a senior tech could fix it immediately is not correct. and I understand that you haven’t dealt with this issue to the extent that someone suffering the problem has, but please be careful with such definitive statements. You chide the users for not having read through the full 18-some-odd page thread. I have. And it’s great that some people have fixed the issue by calling their carriers or toggling Bluetooth but for many folks it’s not that simple.
For the benefit of those actually troubleshooting:
One’s likelihood of getting an uninformed tech at the first level is very high, as you note. That’s true. Higher for Verizon, but not dramatically higher than Apple. Apple’s first level techs are fairly spotty two. On the Apple side you get tech cowboys who assure you they know exactly how to fix the problem but wind up stumped. With Verizon you get script readers who repeat the same process over and over regardless of your reporting that you’ve performed all of these steps numerous times. Anyone who has actually troubleshot the **** out of this thing will tell you that’s true.
At the senior level, both Verizon and Apple have some very well informed, patient, and curious techs. Maybe one in three at Verizon, Apple fifty-fifty.
Apple absolutely altered how MMS permissions worked on iOS last summer, affecting the type of toggles users encounter in the Settings app. Maybe this coincided with a change at Verizon, I don’t know. I don’t know your sources, but there was definitely changes in iOS (I learned this about eight hours into my journey, from an Apple tech).
And yes, the MMS service is handled by the carriers. The permissions for activating/using the service are handled by iOS. It’s not quite so one-sided (that claim is a stubborn pattern in your posts — and I read your posts months ago and used that certainty to lean into Verizon techs, and that’s how I learned what I did, so thank you. But I also learned that your information doesn’t seem to be sourced from actually troubleshooting this issue).
And it’s typical that Verizon has to keep up with improvements to the security features in iOS and they are often playing catchup, but this is an extraordinary case. But to say that, no, it was a Verizon upgrade that broke the function doesn’t ring factual. More like an “I’m rubber and your glue” type response. If Apple was clear on the broken code on Verizon’s side, you can bet they would insist their carrier partner would address the relatively simple problem. Nothing is simple with this one, Lawrence. That’s why the issue persists.
And this is why the problem likely persists. Hot potato syndrome. But that’s just a guess….