Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I got this message the first time I tried to transfer my physical sim to esim from my Xs to 14P. I have Verizon so I knew that it was supported. I just went to the Verizon website, added the iPhone 14P IMEI to my account, then transferred my number to that IMEI. I wouldn’t even bother trying to set up esim through Apple/setup. Just contact your carrier. They’ll know how to get your esim up and running better than Apple.

Side note: Really hating the esim only move still, and now even more so. Really reminds me of the days of the iPhone 4, when us Verizon users had no sim and the phone itself didn’t even have a slot! Not a good throwback though. I was so happy when I got the 5 that there was a (later we found out) fully unlocked sim slot! Was almost a reward for us Verizon users who hadn’t gotten the iPhone until the 4, and then had crappier hardware with no slot. I guess I can hope the 15 brings it back… I won’t hope to hard though.
Thank you for sharing this.

I’ve been dreading this change as well. Back when the iPhone 4 came out on Verizon they were still using CDMA (not GSM standards) which used something called an ESN (like an IMEI but far fewer characters in length) and each ESN had to be registered to the network in order for a phone to work. So you’d have to go through this provisioning process which was a total PITA every single time.

Verizon did have a fairly painless one compared to Sprint. Where you could dial a number and activate a new device that was tied to your account. And you could also manage your ESN associated with each number to a degree online.

Sprint had to have a customer service rep so everything and it generally took ages.

When I worked for the manufacturers in product development we’d usually send spreadsheets with tons of test devices to be “whitelisted” against our accounts so we could activate and test devices on the network.

And yeah we paid for every single line of service. No free testing. LOL

But this move back to a specific line tied to a specific device is tedious as hell. I’ve always hated it and think it’s a generally terrible idea. It just complicates number portability and access as well as device management.

But the paranoid corporations want more oversight and control and micromanagement if every single device connecting to their network.

I don’t see this trend reversing itself.
 
  • Like
Reactions: aPple nErd
Completely agree. WFH also allows a company to hire the best talent from where they are. Some people do not want to relocate.

I tend to think posters who are patently against WFH are probably likely to only have experience in a small company or shop.

Case in point: A friend of mine got a WFH job at a company based in Colorado. Real estate in CO is EXPENSIVE! For him and his family to have to move to CO would spike his fixed costs per month to absurd levels. So he WFH here where the cost of living is way way way less. The company wins too because they don't have to pay him an absurdly high salary to allow him to live in the area and not have to drive hours to get to work every day. Both are happy. He does have to go to corporate every couple of months, but that was suspended recently. It just works for so many companies so well that it just makes sense to do it. There was no reason for him to have to be there. Realizing that freed the company to hire people that they need rather than getting what they could out of the people willing to move there and maybe just scrape by.

There is nothing that would link WFH to shoddy workmanship or customer support except overbearing corporate actors that want to punish WFH employees. So, yeah..
 
Completely agree. WFH also allows a company to hire the best talent from where they are. Some people do not want to relocate.

I tend to think posters who are patently against WFH are probably likely to only have experience in a small company or shop.
Indeed. Or they could also be corporate plants to spread disinformation on the topic.

I know for a fact Apple is having major corporate culture challenges with the move back to work in office vs work from home. It’s caused so much consternation that some talent has been leaving for competitors and senior management is absolutely determined to insist on work in office (per traditional corporate culture) vs work from home or remote.

This comes from the old days when Jobs was in charge. He was adamant about total secrecy with product development and testing. So hai mindset was that the best way to control it is to have a limited amount of people involved in R&D and have them all working on campus in the same area.

It works for smaller entities. But corporations as large as Apple has become its genuinely a challenge and invariably the potential benefits of working in office becomes more and more diluted as teams become divided by regions.

But in general corporate culture at Apple has always been work in office and not from home.

But post pandemic this is not going over so well.
 
  • Like
Reactions: SnappleRumors
Case in point: A friend of mine got a WFH job at a company based in Colorado. Real estate in CO is EXPENSIVE! For him and his family to have to move to CO would spike his fixed costs per month to absurd levels. So he WFH here where the cost of living is way way way less. The company wins too because they don't have to pay him an absurdly high salary to allow him to live in the area and not have to drive hours to get to work every day. Both are happy. He does have to go to corporate every couple of months, but that was suspended recently. It just works for so many companies so well that it just makes sense to do it. There was no reason for him to have to be there. Realizing that freed the company to hire people that they need rather than getting what they could out of the people willing to move there and maybe just scrape by.

There is nothing that would link WFH to shoddy workmanship or customer support except overbearing corporate actors that want to punish WFH employees. So, yeah..

Exactly. There are some limited scenarios where working remotely can be a limitation. It’s usually certain creative roles and certain business development / sales or customer service roles.

But even then. As an executive I would rarely be in my office. I’d most often be traveling all over the place. To customer sites. To engineering sites. To meetings on campus, off campus. Sometimes I would work from home but couldn’t do it for everything.

But working remotely was an absolute requirement because I couldn’t be nailed down to one location and be nearly as effective.

My attitude has always been to enable your team to work under which ever conditions they feel most comfortable and able to deliver.
 
  • Like
Reactions: SnappleRumors
Aren’t those QA guys and girls usually sitting across the globe in India anyway? At least that’s our case
Back in 2016 I applied as a remote senior developer at Apple. Way before Covid. Yes they have resources in India. People just like to blame WFH.
 
Indeed. It’s absolutely and utterly ridiculous. I’ve been advocating remote work as a viable option to most corporations for well over a decade and a half. With very luke warm interest.

There are very few scenarios with the collaboration technologies we have at our disposal that working “in person” is a requirement.

Lots of middle management in the US just gets extremely perturbed at not having direct line of sight to employees and having the satisfaction of strolling the aisles of cubicles to “supervise” their work.

It’s an ego boost. And now that COVID occurred all that middle management became so lonely and ultimately also fear for their jobs. So they don’t like work from home.

Such a glorious waste of operational costs.
Yep. For every employee they have a team leader here 😂 my original comments were also not exclusive for working remotely.
 
  • Haha
Reactions: atomic.flip
Do you not think there would be more issues if there were no developer and public beta tests?
No the issue is that either Apple internal QA is NOT good enough or that marketing is fine releasing poor quality software. This has nothing to do with Beta or developer releases.
 
But it IS TRUE that nothing tests like shipping a product. Seriously. Programmers will likely be nodding their heads enthusiastically yes at that. You can only test what you think might go wrong. Put it in front of users, and just watch the errors pop up.

One testing issue I remember happened not that long ago, and it was a whopper...

The DOD was working with contractors to develop an automated system that could detect (see) enemies in the field to assist troops that were in an area where 'enemies' were believed to be active. They spent millions (of course) on the system and declared that it was nearly 100% accurate at finding enemy positions during testing. So, the next step was to deploy it during a 'war game' and see how it well it worked. They went into the tests with really high hopes. -- AND-- The nearly 100% accurate system was reduced to perform worse than just taking a wild guess. Shocked, they tried to find out why the heavily tested software system had failed. After spending more money trying to defend their system the flaw dawned on one person researching the epic failure. He noticed a pattern that other researchers hadn't, and put the system to the test just like those that 'proved' it was working. It passed his tests. The system had an epic failure. Every image they presented to the system that did not have an 'enemy' was lighter than those that had an 'enemy'. So the 'fuzzy logic' and 'self-learning' system they put their programmers to create *learned* that dark images had enemies, and light images did not. The software system did learn something, that testing bias sucked millions (billions?) of dollars to fund the creation of a system that could 'find' enemies only if they were hiding in a dark area. EPIC FAIL! HYSTERICAL FAIL! I laughed so hard at that...
Classic military contract missed marks. LOL

But you’re absolutely right there is always going to be something that reveals itself that perhaps testing (beyond best efforts) didn’t account for…. But the cultural shift in product development has been towards apathy over testing and allowing the customer to “beta”.

It’s really sad cause any cost savings made by each manufacturer or developer that takes this approach actively rarely makes it back to the consumer.

So the consumer ends up paying for the privilege to do work that was once “expected” of the OEM. Genuinely depressing.
 
iOS and macOS were not perfect on release prior to WFH either. Waiting for the .1 or .2 release didn't start during covid. Apple did whole releases with no new features to only focus on bugs. Trying to blame these or other issues on WFH seem a bit misguided.

More likely, this is another case of Apple's secrecy setting up hard to test situations.
Agreed. I keep bringing up the fact that I received 5 kernel panics a day in Catalina. Which was before WFH. It essentially made my newest Mac useless and it was outside the return window. Luckily I have more than one computer so I just went back to my older one. I literally could not do my job on a new Mac I got and Apple confirmed it was a software issue. And it was fixed on the FIFTH UPDATE!!! Big Sur brought the issue back but it was fixed after the first update.

I bring that up and I hear crickets. It’s like the anti-WFH crowd doesn’t want to hear or believe there were some very VERY big issues even before WFH.

Case in point Apple has created the absolute best macs in I’d say a decade or even two with the M1 laptops. All with WFH mixed in. Macs are INCREDIBLE now. Finally. Ever since the 2010 Mac Pro I haven’t been happy with macs.
 
  • Like
Reactions: Violet_Antelope
Fortunately,I never seem to experience all these bugs 🙂
I am with you, but I know why. I never, ever buy newly released Apple products these day. If you wait until x.4+ then you have a much better chance at getting the old Apple experience (it just works). Of course, you still have to wait for x.6+ to get all of the announced features.
 
Agreed. I keep bringing up the fact that I received 5 kernel panics a day in Catalina. Which was before WFH. It essentially made my newest Mac useless and it was outside the return window. Luckily I have more than one computer so I just went back to my older one. I literally could not do my job on a new Mac I got and Apple confirmed it was a software issue. And it was fixed on the FIFTH UPDATE!!! Big Sur brought the issue back but it was fixed after the first update.

I bring that up and I hear crickets. It’s like the anti-WFH crowd doesn’t want to hear or believe there were some very VERY big issues even before WFH.

Case in point Apple has created the absolute best macs in I’d say a decade or even two with the M1 laptops. All with WFH mixed in. Macs are INCREDIBLE now. Finally. Ever since the 2010 Mac Pro I haven’t been happy with macs.

The M1s and hopefully M2s as well are indeed fantastic machines. Sadly I own neither. Last major Apple. Computer purchases were two fully loaded 2019 16” MacBook pros. Luckily I got the ones with the 5600m in Q1 2020 but I feel like I missed the boat with the release of the M1s less than a year later.
 
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.
 
Is it just me or does this iPhone 14 release just seem like a rolling headache? It’s been on issue after another with the new phones, i have the 14 Pro Max and and have had my share of frustrations with the device. Already 3 patches in and the bad news just continues.
 
  • Like
Reactions: Violet_Antelope
Agreed. I keep bringing up the fact that I received 5 kernel panics a day in Catalina. Which was before WFH. It essentially made my newest Mac useless and it was outside the return window. Luckily I have more than one computer so I just went back to my older one. I literally could not do my job on a new Mac I got and Apple confirmed it was a software issue. And it was fixed on the FIFTH UPDATE!!! Big Sur brought the issue back but it was fixed after the first update.

I bring that up and I hear crickets. It’s like the anti-WFH crowd doesn’t want to hear or believe there were some very VERY big issues even before WFH.

Case in point Apple has created the absolute best macs in I’d say a decade or even two with the M1 laptops. All with WFH mixed in. Macs are INCREDIBLE now. Finally. Ever since the 2010 Mac Pro I haven’t been happy with macs.

I just remembered investigating an issue pertaining to the kernel panic issue that had been plaguing macOS on mostly mobile devices (laptops/MacBooks) from 2019 through to 2020.

If I remember correctly it was due to a low level driver for an Intel component on the logic board that needed an update from Intel specifically. (They package the drivers into MacOS). It was causing a KP each time the machine would try to go into suspend / power saving mode.

It was infuriating as it also affected my (at the time) primary machines.

So from my lab (at home), I ran through testing scenarios to identify the culprit then wrote up a succinct account of the problem and recommendation for resolution.

I actually ended up sending it off to TC to forward to whom ever would be best at Apple. But the problem was bad enough I thought it needed priority attention.

He did not reply directly to that note (has in the past on other matters) but it was quickly handled in the following two weeks and the KPs stopped happening like clock work.

TC is way too busy to answer most emails directly now but his staff does review and triage messages (even from customers) and if you do your due diligence they do a good job of incorporating feedback into their dev process.

And keep in mind there are other people I could have reached out to at Apple (No not customer service or Apple care) but this was a particularly nasty bug causing lots of data loss for MacBooks. And yes I absolutely did file tickets with Apple Care and walk through the tedious but necessary process of user reporting and working with AC engineers.

Honestly Apple still has one of the best customer service experiences you can get from almost any consumer electronics company.
 
.....
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 we can now assume that management could care less about bugs. They don't listen to their software developers or managers, or their software management is incompetent in handling bugs. Both are the responsibility of Sr. Management.
 
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.
This bug has been happening on at least the last two major OS revisions. Sometimes you have to setup the damn thing from scratch.

The HomePod is in serious need of attention.
 
Is it just me or does this iPhone 14 release just seem like a rolling headache? It’s been on issue after another with the new phones, i have the 14 Pro Max and and have had my share of frustrations with the device. Already 3 patches in and the bad news just continues.
Yeah. It’s been particularly bad this time around. I don’t think work from home is the primary cause. But the pandemic has impacted testing and development even in China so teams that would normally collaborate were less able to do so because of illness. (Not because of location.)
 
I don’t come on here for a freaking ego boost. I research and study new mobile devices from multiple manufacturers. I don’t work for a carrier or for a manufacturer. I advise corporations on how to invest in mobile tech and other user interfacing technologies. So even if I’m not personally affected by a workflow challenge then yes I study it and find solutions to work around them or note the workflow challenge in recommendations made to clients.

Been working in the industry for 25 years and while I appreciate your enthusiastic support of any manufacturer. It’s painfully obvious you’re a fan and just blowing smoke to get some sort of rise out of people online.

Like I said, if you have something of value to contribute go ahead and comment. Don’t waste my time or anyone else’s with constant droning about how perfect your device is or how people shouldn’t discuss problems here because everyone has them. Your attitude is the sort of thing that at best kills IT departments at many companies.

Your job would have been outsourced ages ago if you took that attitude with your users.

Oh and PS: Hyperbole is an exaggeration. Please use a dictionary when referencing word meaning.
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.
 
I’m curious. Did you have Verizon prior on your old device? Did you migrate your sim from the old phone to the new one or activate the new phone directly on Verizon without transferring the sim?

Thanks!
My old phone was on VZW on iOS 15(in fact it was an xr if that makes a difference). Using the built-in iOS functionality I co-located the two phones and let the transfer do its thing. The esim process took a few seconds and the entire process took about 30 minutes. I received an email from VZW saying that the plan had been updated to 5G, but I was already on a get more plan with 5g included.

So the transfer to the esim was automatic. There was a message on the iPhone 14 PM stating the phone was activated on VZW.
 
  • Like
Reactions: atomic.flip
Agile is why I stopped software development as my day job. Well a better way to say a dozen companies I worked for and how they use agile is why I stopped.

As one of the people who’d often be responsible for brokering a deal between engineering and the customer…. Agile has always felt like a means of attempting to piecemeal features and functions to a customer who is hoping for a much more fleshed out product.

The breakdown that seemed to most often be the issue is “interdependency”. And guaranteeing “development” on a schedule is tenuous at best.

Basically it’s trying to put a degree of artistry on the production line. And as you know software development can be much more nuanced based on user design requirements and entirely unforeseeable soft interdependency changes.

I’ve never had a single agile delivery result in what I would call a finished product.

But I did bust my rump to firewall the dev teams held to that standard.

What did you end up switching to if I may ask?
 
  • Like
Reactions: LightsOn45
My old phone was on VZW on iOS 15(in fact it was an xr if that makes a difference). Using the built-in iOS functionality I co-located the two phones and let the transfer do its thing. The esim process took a few seconds and the entire process took about 30 minutes. I received an email from VZW saying that the plan had been updated to 5G, but I was already on a get more plan with 5g included.

So the transfer to the esim was automatic. There was a message on the iPhone 14 PM stating the phone was activated on VZW.
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.
 
  • Like
Reactions: I7guy
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.