Affiliate Disclosure
If you buy through our links, we may get a commission. Read our ethics policy.

Don't install Apple's new betas — let others risk their devices

Really bricking your iPhone doesn't look this good.

Last updated

Every year Apple releases beta test versions of its newest software, and every year people lose data, time, and money to it. If you value any of those, wait.

You may have been lucky so far, but this is beta roulette — at some point, you're going to have a problem. The thing is, it's potentially such a big problem that when it happens, at the best, you lose time.

More severely, you can lose data. And, in extreme situations, you can stop your device from working at all.

Completely bricking your device is fortunately very rare. The trouble is that you have no way to figure the odds of any of the three scenarios happening.

It's not worth installing the new beta iOS, iPadOS, macOS, watchOS, tvOS, or visionOS, even though it will be enticing. All of them will have compelling new features — well, except perhaps tvOS — but you can use and enjoy them when Apple officially releases it all in a few months' time.

Even then, if you rely on your devices to make money, you'd be better off waiting a little while before installing them. But while they're in beta, you are putting your devices and data at risk.

According to Bloomberg, and things we've heard ourselves, things look worse this year.

It's probably not consoling that reporting lost data or incredibly hard crashes on your iPhone helped other devices to live. But that is literally the main reason that there is a beta release at all.

True, developers do need the new versions to test against their apps, but otherwise this is Apple exposing the new OSes to more users and in more situations than they could ever test internally.

AppleInsider staff can promise you that when severe problems happen because of the betas, it doesn't feel like that. Your expensive device, the device you rely on every day, chewing on your data or not working at all is time-consuming.

And, time you've spent recovering that device is time you're not making money, or spending it on things you want to spend it on.

Collateral damage

There is always the chance that your device and data are going to be fine. The new OSes will have gone through alpha testing inside Apple, after all.

You could very well be lucky and be one of the people whose devices are not impacted, and have a very smooth experience.

Since there is no way to know that's the course things are going to take without risking your device, it is truly not worth it. Maybe you'll get lucky again, who knows.

But that's the problem. You don't know if things are going to go well or poorly. Last year's experience, or 10 years ago's install, aren't any indicator of success now.

That business of developers getting early access is not because they have devices to spare. It's not even so that developers can add in new features to take advantage of whatever improvements Apple has offered.

At this stage of the game, it's more so that developers can ensure that their apps still work on the latest version. Very many will not.

Red brick with three holes placed next to a white computer keyboard on a wooden surface. It may be completely unusable, but it's got great new macOS features

At the extreme, some apps may not launch. Any app can have a feature that suddenly stops working.

It could be that the developer just has to do something impossibly tiny to make it all work again, but until they release an update, you're stuck without a feature you rely on to make your money every day.

Developers who've been through this before also know that if the first beta breaks a feature of theirs, a second beta could break whatever fix they do. So at least some developers will wait for weeks or months into the beta test before they release an update.

Others will be working on updates but not release them until Apple does the final, public version.

Then when you've waited through the months of beta updates all the way up to the time when Apple starts pre-installing the new version on devices, other app developers will wait even longer.

That's because while the beta exposes Apple's new software to many more people than it could ever get in an internal test, that's still a tiny proportion compared to the number of people who use and rely on these OSes. Once they come out of beta and become the official public release, millions upon millions more people will use them — and they will find more bugs.

This all sounds as if Apple releases badly-made software, and sometimes it does. But nobody at Apple will thank you for sacrificing your devices to find out. You're not going to get a check if all your Contacts are wiped out, or Photos eats every single one of your pictures going back over a decade and then propagates that to iCloud, which then in turn wipes them all out, everywhere.

In the coming days, weeks, and months, you are going to be able to read about every detail of the new OSes — and their bugs — on AppleInsider. But this is not a case of do as we say, not as we do.

Instead, it's a case of every team member having a spare device explicitly for testing. It's a case of dedicated hardware for beta testing, and no one is going to let the betas near their main work devices.

And in most cases, we're not letting it near our main iCloud account either.

We're not the only ones saying this. Apple says it too on that license most click through without reading.

So, if you don't listen to us, that's fine. Listen to the folks that made the betas instead when they say that if you value your devices and time, or use your machine for your day-to-day, wait. It's just not worth the potential for disaster.



10 Comments

rezwits 856 comments · 17 Years

Some people say wait wait wait etc, but if you really can't risk the device, wait at least till ßeta 2...

There have been beta 1s that have bricked devices... I had one, a MacBook 12-inch 2017, warped hard... iCloud got all jacked on the device couldn't repair for nothing the backup etc, had to reformat and reinstall which was such a pain back then tho, cause of the one port; now wasn't an absolute brick but it was scary that my iCloud was gonna get screwed...

I am gonna wait till ßeta2...

my 2¢

jagrahax 11 comments · 1 Year

Thanks William.  I always wait for Beta 6, which usually shows up in mid-August. 

Mike Wuerthele 6906 comments · 8 Years

rezwits said:
Some people say wait wait wait etc, but if you really can't risk the device, wait at least till ßeta 2...

There have been beta 1s that have bricked devices... I had one, a MacBook 12-inch 2017, warped hard... iCloud got all jacked on the device couldn't repair for nothing the backup etc, had to reformat and reinstall which was such a pain back then tho, cause of the one port; now wasn't an absolute brick but it was scary that my iCloud was gonna get screwed...

I am gonna wait till ßeta2...

my 2¢

Last year, in what was supposed to be a quiet year for updates and big changes, the betas just kept crashing and necessitating a reinstall on my Mac, over and over. Wasn't fixed until beta 4.

So yeah, it happens. And when it happens, it can get bad.

We've gotten some pushback on social about this, from folks that really have no business running the betas as they have nothing to test, and won't report back to Apple. We've even had some here already complaining that they know this already, and why should they have to be told it again.


It's just sound advice to wait if you need stability. And, AppleInsider is for everybody.

dewme 5775 comments · 10 Years

Whichever beta you decide to take a leap of faith on, if any, at least go with the public beta. By then the worst casualties from the dev beta should have surfaced. But as everyone has said repeatedly, never install betas on business critical machines or any personal machine that you would be seriously inconvenienced if things go wrong.

MacPro 19845 comments · 18 Years

Another warning story.  I have several spare Macs, and each year around this time, I select one (I have a spare M1 Studio this year), clone the working current drive with Carbon Copy Cloner, set that aside, and install the beta with my developer account access.  This may seem safe, but I vividly remember many years ago, linking the beta to my iCloud account was a temporary disaster as once done, the Photos library on the cloud was no longer available to all the other devices until months later, they were also able to upgrade.  Since then, I haven't linked the non-public beta to my working iCloud account. I suspect the answer is to have a separate iCloud account, but I have never gotten around to bothering with that so far.