Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
The hyperbole is not an exaggeration. I dislike faux outrage. Point is this is a bug. Hopefully the carriers and apple can get together to address this.
Ultimately we all want the same thing. Just to find a solution to the issue.

I am hopeful they will implement the change I suggested or at least give the user the option of deleting the problematic eSIM and then reprovisioning if required.
 
Ok that sounds like the exact process that is expected.

You wouldn’t run into the scrnario I’m describing unless your phone was locked to Verizon and you tried to add an eSIM from T-mobile, AT&T or what ever.

I’m hoping my transfer will go as smoothly as yours did. Haven’t done it yet as I’m still waiting for my 14 PM to arrive.

I’ll be moving from Dual SIM (Verizon physical and T-mobile e-SiM) to Verizon eSIM only for the first 60 days. Then I’ll move my T-mobile line over to that phone as well.

I’m hoping and I don’t know if this is happening (no one has reported this to me or on any engineering forums I frequent) that there isn’t another problem triggering the eSIM to become flagged as invalid or unsupported. As the same workflow issue would come up and that would presently suck.

Thanks for sharing your experience.
Those locked phones, due to the unsavory finding loopholes in the activation process, are what caused this to begin with. I find the concept of locked phones to be the utmost in consumer unfriendliness.
 
I wonder has this problem happened with T-Mobile USA users transferring from older iPhones to the iPhone 14 models.
It should only happen if you are moving from a device on another network and your phone is subsidized (meaning you didn’t pay full price for it).

That’s the most likely scenario.

But in general the way the phone handles an eSIM it can’t authenticate or validate (assume data corruption or random bad luck) is it blocks the use of the device due to an immediate check on SIM validation before the user is able to interface with the OS at all.

It’s important to note that eSIMs in general are activated on boot up before physical SIMs.

I see this with my iPhone 13 PM all the time where my T-mobile e-SIM will be fully connected sometimes several seconds before the Verizon physical SIM is connected.

This maybe due to slower hardware interfaces between physical SIM vs eSIM running in memory exclusively.
 
Absolutely. WFH decreases quality. Hybrid is not much better.




This is Tim Cook's nice way of saying WFH has caused a decrease in productivity, creativity, and quality.

Tim Cook has all the data that suggests WFH does not work. He is calling all workers to return to the office. Anonymous Macrumors forum posters do not have more data than Tim Cook no matter how confident they sound in their forum posts.
This is all conjecture on your behalf as well.
 
  • Disagree
Reactions: Babygotfont
Those locked phones, due to the unsavory finding loopholes in the activation process, are what caused this to begin with. I find the concept of locked phones to be the utmost in consumer unfriendliness.
I know and agree completely. Most consumers that sign an agreement with a carrier to receive a subsidized device in exchange for committing to a period of service honor their commitment with no issues. But way too many people try to scam the system to export devices and sell them at tremendous mark up’s overseas.

This phone trafficking as well as customer retention concerns from carriers have been concerns for a while.

The first scenario I can understand the desire to lock devices. And that’s why Verizon has their 60 policy. It discourages trafficking. But they then promptly and automatically unlock all their devices. It’s a great policy in my opinion.

But the carriers who refuse to unlock or try to hold customers hostage to their network by only providing locked devices (happens to some post paid accounts overseas) really irritate me.
 
Is this some sort of problem with phones worldwide? Or just with those USA e-SIM only phones?
That is my question as well!! Is it just the U.S., or everyone else but the U.S. that has this problem?

SO I guess, has anyone hit this message, and if so, what kind of phone? (U.S. only or other)
 
This community's hate for WFH is so weird. Makes me think people are just bitter.
99% of the population against WFM consists of middle management (by this I mean managers who have or use no specific technical or business skill outside of “people” resource management).

Keep in mind that to them their “resources”’are people. And if they’re expected to assure productivity is occurring and that’s all they do then it can be unsettling to suddenly have everything you’re supposed to be overseeing taken out of your direct line of view.

But this is a very archaic mode of thinking about and managing productivity.

At the end of the day you can’t attach yourself to people’s backs to ensure they’re doing very thing you want the way you want them to 24/7.

That sort of insecurity would be the functional equivalent of Tim Cook insisting he should personally hand deliver every single iPhone from factory to customer to ensure each customer experience is exactly how he believes it should be.

Time management requires you develop trusted relationships with partners, vendors and yes your direct employees.
 
  • Like
Reactions: Pushpaw and bpeeps
That is my question as well!! Is it just the U.S., or everyone else but the U.S. that has this problem?

SO I guess, has anyone hit this message, and if so, what kind of phone? (U.S. only or other)
It’s only a problem for eSIM only.

But…. It could happen on a carrier locked SIM and eSIM phone that is somehow provisioned with an eSIM from another carrier.

Technically this is a workflow oddity that became a problem that is much more prevalent with the switch to eSIM only. But it’s been an issue that needed to be addressed for a while.

It was just far less likely to occur before.
 
  • Like
Reactions: brgjoe and bobcomer
Now if they'll acknowledge that iOS 16 has screwed up all HomePods but most screwed up is the OG HomePod. Planned obsolescence? My Home app says my apple password is wrong on ALL HomePods. I sign in to each HomePod (each one accepts the password) and 5 minutes later, same message.
Plus Siri is still dumb AF on the HomePods. It’s a chore getting it to play some songs just because Siri, itself mispronounces them (like “CUFF IT” by Beyoncé).
 
I'm one of the biggest Apple fanboys but why is that belief acceptable for some?

No there shouldn't be bugs when you're a trillion dollar company and launching a new operating system for one of the world's leading smartphones.

The list for this latest release continues to grow. I'd love to be a fly on the wall inside Apple and hear how they react to news of more bugs.

I think Apple needs to do bi-annual OS releases - the operating systems are being rushed out the door and the consumer is left to be the guinea pigs.
Agreed with this. And not just Apple. Microsoft, Adobe and many others need to stop yearly or twice a year big updates.

But even so bugs will always exist. It’s not the fact that Apple is a trillion dollar company. Humans write the software, and we are not perfect 100% of the time.
 
It’s only a problem for eSIM only.

But…. It could happen on a carrier locked SIM and eSIM phone that is somehow provisioned with an eSIM from another carrier.

Technically this is a workflow oddity that became a problem that is much more prevalent with the switch to eSIM only. But it’s been an issue that needed to be addressed for a while.

It was just far less likely to occur before.
So I guess I just don't add another eSIM until my Verizon locked for 60 days phone gets unlocked. I'm glad I don't travel!
 
This OS in new iPhones it’s being buggy. I have some in my 14PM. Minor but there are. Not happening in the 13PM I had before.
And phones are not so different in hardware, apart from island and interface differences caused by that.
They will polish it but is hard to understand anyway.
 
  • Sad
Reactions: Babygotfont
So I guess I just don't add another eSIM until my Verizon locked for 60 days phone gets unlocked. I'm glad I don't travel!

Just buy iPhone from oversea. Problem solved.

I love what apple send to me on my complaint of ESIM only option for us.

Like I already don’t know it.

BTW- M1 prepaid esim isn’t available at Changi. It’s only offered at corporate store which is far away from airport.

Chunghwa telecom also have same policy- prepaid esim only at corporate store and none at airport :)

I really wonder if Apple really thought through when some MBA graduate figured it’s more important to save couple dollar then creating whole loads of problem with esim only approach.

9C9BEA78-ADFD-4F4C-BDA5-1F72A1C88C1E.png
 
The iPhone 14 Pro Max is one of the buggiest iPhones I’ve ever had, I started at the iPhone 3G. Sometimes I just put it away and use my iPhone 13 mini. I’m sure they’ll fix it.
 
Just buy iPhone from oversea. Problem solved.
That's pretty hard retroactively. :)

I really wonder if Apple really thought through when some MBA graduate figured it’s more important to save couple dollar then creating whole loads of problem with esim only approach.
I don't know what Apple is thinking other than acting the bully and forcing change. eSIM is actually great -- when it works and you can get the eSIM you need. The trouble with the U.S. iPhone is it lacks any kind of backup if eSIM doesn't work for you. I do have backup, but that's another phone and line that's not an Apple phone. (Samsung Flip4) and I'm getting closer and closer to preferring it over the iPhone. The only bug I've hit with it is it boots into safe mode after a security update for some reason, which is annoying but not a showstopper.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.