{"id":25926,"date":"2019-07-11T16:38:59","date_gmt":"2019-07-11T20:38:59","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=25926"},"modified":"2019-07-11T20:39:48","modified_gmt":"2019-07-12T00:39:48","slug":"icloud-data-loss-with-macos-10-15-and-ios-13-betas","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2019\/07\/11\/icloud-data-loss-with-macos-10-15-and-ios-13-betas\/","title":{"rendered":"iCloud Data Loss With macOS 10.15 and iOS 13 Betas"},"content":{"rendered":"

Max Seelemann<\/a>:<\/p>\n

Whereas in recent years, it was pretty safe to install preview versions early on, this year that’s definitely not the case (see for example this report on Cult of Mac<\/a>).<\/p>\n

Most impactful for us, however, is that the (great, great) updates done to iCloud are also leading to severe problems with the service. As iCloud is Apple’s sync service, it’s beyond our power to solve them, of course. Some public beta users reported synchronization outages and data loss that propagated to devices that did not even run the beta<\/em> but were just connected via iCloud.<\/p><\/blockquote>\n\n

Craig Hockenberry<\/a>:<\/p>\n

\n

If you have an iOS or macOS beta installed, disable iCloud on that device NOW.<\/p>\n

If you don’t you’ll end up with data loss on your production devices. Also, these problems are not app-specific, things are fucked up at the framework level.<\/p>\n<\/blockquote>\n\n

Judging from the release notes, Apple knew about many of the issues prior to releasing the betas, so it’s surprising that they chose to release the public betas earlier this year.<\/p>\n\n

John Gruber<\/a> (tweet<\/a>):<\/p>\n

\n

Right now iCloud is dangerous on the beta OSes. That’s not a complaint in and of itself; if there weren’t bugs they wouldn’t be betas. But I think it was a bad idea for Apple to release public<\/em> betas at this stage.<\/p>\n<\/blockquote>\n\n

Craig Hockenberry<\/a>:<\/p>\n

\n

Apple talks a lot about services being the future of the company, but then they pull shit like this and it makes me wonder if they have any clue that the most important part of a data service is protecting its contents.<\/p>\n<\/blockquote>\n\n

Wil Shipley<\/a>:<\/p>\n

The real BS part of this is that there’s really no good way for us to restore<\/em> iCloud data, which is becoming increasingly more of our data.<\/p><\/blockquote>\n\n\n

Max Seelemann<\/a>:<\/p>\n

\n

I<\/em> know what a beta is and what that means. But in times where everything is a beta, people tend to to forget.<\/p>\n

imo, a company giving betas to millions of people is responsible for doing this in a responsible manner. As a minimum it’s to make sure to at least not delete data.<\/p>\n<\/blockquote>\n\n

Colin Weir<\/a>:<\/p>\n

\n

There’s also an implied level of stability in a public beta that’s not in a developer beta. We know they’re basically the same builds, but to normal users “public beta” means “safe, but some stuff might work weird\"<\/p>\n

So by putting out unstable developer betas and calling them public betas, they’re doing a big disservice<\/p>\n<\/blockquote>\n\n

Steve Troughton-Smith<\/a>:<\/p>\n

\n

iBooks is unusable in iOS 13 thanks to iCloud issues. It took three weeks (!) for it to re-index my iCloud library before it would let me open a book, and it deletes it and requires a redownload, citing space issues, constantly (I have 180GB free space). Local cache is whack<\/p>\n

It’s definitely not the worst beta process by a long shot, but it’s definitely way too rough for public seeding on iPad. I’m losing touches constantly, which makes the software keyboard as bad as the MacBook Pro for reliability At least they’re consistent…<\/p>\n<\/blockquote>\n\n

Craig Hockenberry<\/a>:<\/p>\n

\n

We submitted a detailed DTS incident about corrupted\/deleted iCloud documents in the iOS 13 beta. But guess what? DTS doesn’t support beta releases.<\/p>\n

So it’s a public release, but not.<\/p>\n<\/blockquote>\n\n

Steve Troughton-Smith<\/a>:<\/p>\n

\n

from what I’ve seen, a lot of the time I run into ‘data loss’ is where some migration\/indexing process has got stuck, making it look like I’ve got no\/wrong data, and instead of waiting it out I try and fix it myself while the system is still broken<\/p>\n

It’s very<\/em> easy to panic and do a lot of damage when the OS makes it look like your data is screwed up, even when underlying data is totally fine and it’s actually some intermediary daemon process hanging in the bg. Sometimes you really do need to chill & wait for the next beta<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n