In recent years, it was quite safe to install preview versions early this year, which is definitely not the case (see, for example, this report on the Cult of Mac).
Most effective for We are, however, that the (big, great) updates made to iCloud also cause serious service issues. As iCloud is Apple's synchronization service, it's beyond our power to resolve them of course. Some public beta users reported sync violations and data losses that spread to devices who did not even run beta but were only connected via iCloud.
If you have an iOS or macOS beta installed, disable iCloud on that device NOW.
If you don't want to end up losing data on your production units. Also these problems are not app-specific, things get fucked up at the frame level.
Daughters from the release notes, Apple knew about many of the issues before releasing the beta, so it's surprising that they chose to release public pastures earlier this year.
John Gruber ( tweet ):
Currently, iCloud is dangerous on the beta operators. It's not a complaint in itself; if it were not wrong, they would not be grazed. But I think it was a bad idea for Apple to release public grazed at this stage.
Apple talks a lot about services that are the future of the future company, but then they wonder so much and that makes me wonder if they have any idea that the most important part of the data service protects the content.
I know what a beta is and what it means. But in times when everything is a beta, people tend to forget.
Imo, a company that provides grazing to millions of people, is responsible for doing so responsibly. At least make sure you do not delete any data.
It is also an implied level of stability in a public beta that is not in a developer beta. We know that they are basically the same, but for normal users, "public beta" means "safe, but some things work fine"
So, by putting out unstable developer grapples and calling them public beetles, they make a big belief service
iBooks is useless in iOS 13 thanks to iCloud issues. It took three weeks (!) To re-register my iCloud library before it would let I open a book, and it deletes it, and requires a download, citing spaces, all the time (I have 180 GB of free space.) Local cache is munching
It's definitely not the worst beta process of a long shot, but it's definitely a way too heavy for public sowing on the iPad. I lose touches all the time, which makes the software keyboard as bad as the MacBook Pro for reliability. At least they are consistent …
We sent a detailed DTS event about corrupt / deleted iCloud documents in t he iOS 13 beta. But guess what?
So there is a public release run into "data loss" is where some migration / indexing has been stuck, so it looks like I have no / wrong data, and instead of waiting for it, I try to fix it even while the system is still corrupted  Very is easy to panic and do a lot of damage when the operating system makes it appear that your data is turned up even when underlying data is fine and there is actually some intermediary daemon process that hangs in the BG. Sometimes you really need to relax and wait for the next beta
Stay updated by subscribing to the RSS feed for this post.