Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Bug in iOS 8's 'Reset All Settings' Option Also Erases iCloud Drive Documents
- Thread starter MacRumors
- Start date
- Sort by reaction score
So assuming there's another patch to fix this bug, will this be the fourth third iOS 8 update in ... two weeks?
Actually it allowed them to keep guessing passwords over and over without locking them out. iCloud was protected against this but not Find My iPhone (I think that's the service the hackers got in through) BUT Apple was warned 6 months prior about this bug and their response was it would take too long for someone to figure it out. Apple's arrogance is coming back to bite them in the butt, they need to wake up and get back to basics.
I think I'm the person quoted in the article who first reported this problem.
Firstly let me say I'm surprisingly chilled about it and Apple have been more than helpful, despite not actually recovering my data yet. I think the problem is an interaction between using Yosemite iCloud Drive and iOS 8. Perhaps some of you not replicating it are not using iCloud drive?
Secondly in terms of the why the f@@@ don't I back up my data I do the following:
Store my documents in iCloud Drive and have local synced copies of those documents on all iOS devices. This should really be ok in itself.
Back up my devices to ICloud regularly - but seemingly iCloud devices backups don't include documents that already exist in iCloud
Back up to time machine
Back up to back blaze.
Several have advised me my documents must have existed on my hard drive (as there are presumably local copies on my Mac that also sync with iCloud ) and these should be theoretically recoverable via the time machine back up or back blaze. However they are not. Time machine will not roll back to show me previous documents in the mobile documents folder. I can't explain why (Yosemite??) but I can promise you they seemingly don't exist in any historical backup either.
You know stuff happens. You can't expect perfection with complex stuff like this. But what I'd like to see is a trash in icloud. Just that please, and I can use my own small brain to manage such issues myself. Like I can with Dropbox.
Fortunately for me I had a work iPhone that I hadn't updated to iOS 8 and this had been divorced from syncing with iCloud drive ever since I upgraded to Yosemite beta, It had some 2 month old versions of most documents on it and when I (saved all the key documents on my Mac desktop first, held my breath and) updated to iOS 8, it copied these outdated documents to iCloud. In the end I'm only missing 2 or 3 key documents. I was luckier than some.
Any ideas on recovering from backups welcome, but I honestly DO back up, am not completely stupid, and they really don't seem to be there.
Firstly let me say I'm surprisingly chilled about it and Apple have been more than helpful, despite not actually recovering my data yet. I think the problem is an interaction between using Yosemite iCloud Drive and iOS 8. Perhaps some of you not replicating it are not using iCloud drive?
Secondly in terms of the why the f@@@ don't I back up my data I do the following:
Store my documents in iCloud Drive and have local synced copies of those documents on all iOS devices. This should really be ok in itself.
Back up my devices to ICloud regularly - but seemingly iCloud devices backups don't include documents that already exist in iCloud
Back up to time machine
Back up to back blaze.
Several have advised me my documents must have existed on my hard drive (as there are presumably local copies on my Mac that also sync with iCloud ) and these should be theoretically recoverable via the time machine back up or back blaze. However they are not. Time machine will not roll back to show me previous documents in the mobile documents folder. I can't explain why (Yosemite??) but I can promise you they seemingly don't exist in any historical backup either.
You know stuff happens. You can't expect perfection with complex stuff like this. But what I'd like to see is a trash in icloud. Just that please, and I can use my own small brain to manage such issues myself. Like I can with Dropbox.
Fortunately for me I had a work iPhone that I hadn't updated to iOS 8 and this had been divorced from syncing with iCloud drive ever since I upgraded to Yosemite beta, It had some 2 month old versions of most documents on it and when I (saved all the key documents on my Mac desktop first, held my breath and) updated to iOS 8, it copied these outdated documents to iCloud. In the end I'm only missing 2 or 3 key documents. I was luckier than some.
Any ideas on recovering from backups welcome, but I honestly DO back up, am not completely stupid, and they really don't seem to be there.
Actually it's a very fair test, because where the force is applied, it will find the weak point. Just because a force is applied in the centre, doesn't mean that's where the deformation will be.
You're using someone's best guess as to where the weak point is. Now their reasoning has plenty of sense behind it, however they aren't necessarily right.
What are you saying... the weak point is pretty specific due to the metal holding the volume buttons - the tests showed that it was bending in the middle, not where the weak point is. It's also interesting how the tests show that the iPhone 6+ was harder to bend when this is the model where the 'bengate' is a real issue with there being few iPhone 6 reports.
The aluminium is pretty strong and wouldn't bend normally, but the issue is the specific weak point which is why this test wasn't fair. They should have done the test at 3 different points along the phone.
Regardless there's never been a bend issue on this scale on other phones so saying they all have the same durability is naive.
I'm in virtually the same boat. I'm lucky that I have a machine that hadn't been updated to Yosemite yet so it still had a copy of most of the iCloud stuff.
It's true that Time Machine does NOT back up iCloud Drive on Yosemite. I have two machines with separate backups and this is the case. This seems to be a pretty egregious oversight combined with no Trash option on iCloud Drive.
I have a call scheduled this afternoon for some "advanced troubleshooting" so we'll see if anything productive comes of that.
edit: It occurred to me to try my Mavericks machine and it does indeed allow you to view and recover Pages/Numbers/Keynote docs prior to iCloud Drive. That might help someone.
This is such a glaring oversight, it's MIND BOGGLING that a company like Apple would not enable Time Machine backups for iCloud Drive.
Even if the data is both on your Mac and in the cloud, it appears being deleted in one place also deletes it in the other. On top of that, there is no way to roll back to a previous date. These are things that Time Machine can fix; why the hell isn't it implemented?
Guess you didn't read what I wrote. I said it's getting worse and worse which it is. Each "update" yields more problems and more serious ones at that.
Your dribble about Android is irrelevant to what I said in my post
Yes it truly is. It makes me think that there must've been technical reasons for doing what they did. Otherwise it just seems like such a glaring oversight that a company like Apple Couldnt possibly make.
The consumer wanted bigger iPhones. They are not pointless.
----------
You really have no idea what you are talking about
I have lost data and unfortunately for me, although I am (or was!) in the Apple camp when it comes to all mobile devices in our household we still use the other major OS when it comes to laptop and desktop computing. So I didn't have the option to backup iCloud documents
I have seen reports that this bug only affect those that are using both Mac OS and iOS devices but I can confirm that even if only using iOS devices the reset will wipe your iCloud.
The Windows iCloud app now creates a folder of iCloud Drive in File Manager; which it didn't before. So I know what I will be doing if Apple recover the files... making regular backups of this folder. Before, one had to go to clunky iTunes and copy across hundreds of files which wasn't practical. I put my faith mistakenly on iCloud being the backup in itself.
Holy what? I am in very much the same boat. I had saved VERY IMPORTANT CLIENT DOCUMENTS in iCloud because I assumed that would be the safest place to put them (cloud sync + cloud backup + local time machine backup). RIGHT?
Why are mobile documents not recovering properly? There surely MUST be a physical copy somewhere in my backup, right?
Just going to cry now. How are Apple not able to recover the things we trusted them with? When we clearly have physical copies on our machines as well as on their servers which must get backed up to prevent just these sorts of F-ups? Data does not simply disappear these days!!
Last edited:
It took quite a while, including talking to someone who tried to tell me that iCloud Drive was still in Beta, but I talked to a senior adviser who put my iCloud account in troubleshooting mode. He said the engineers will take a look at the account and I should hear back in the next day or two.
Not to let you down before Apple does, but Apple did the same exact thing with my accountunfortunately to no avail. I sincerely, sincerely hope you yield a different result (after all, it's been two months since they looked at my account).
Please post back with whatever happens!!!
Thanks, I'm not getting my hopes up and I DO have most of what I need from my Mavericks computer.
But this is a HUGE flaw, particularly in light of the fact that Yosemite Time Machine doesn't back up iCloud Drive.
I received a reply to my followup request from the Apple senior advisor who was working on my case. He just reconfirmed the bad news along with an "explanation" of what happened. He said in part "...They have reported to me that they are unable to restore any of your documents. It seems like during the migration to iCloud drive your uploaded documents did not make it all the way back up to iCloud....Ive asked two separate engineers and we are unable to restore them."
Nice half-assery, saying FRONT pockets. Some of us men require a phone that can survive a BACK pocket. A wallet goes in one front pocket, keys in the other. That leaves only back pockets for a phone. Maybe you don't mind looking like a dumpy schlub, but some of us do.
Apple sure has been shooting themselves in the four lately.
iCloudgate, bendgate. Then IOS 8.01 bricks 40000 phones. Now IOS 8.02 erases iCloud data. What gives Apple?
Now Bluetooth isn't working too?
https://www.macrumors.com/2014/10/01/ios-8-bluetooth-connectivity-issues/
iCloudgate, bendgate. Then IOS 8.01 bricks 40000 phones. Now IOS 8.02 erases iCloud data. What gives Apple?
Now Bluetooth isn't working too?
https://www.macrumors.com/2014/10/01/ios-8-bluetooth-connectivity-issues/
Last edited:
Doesn't the wallet typically go into the back pocket? Sitting down on a phone (with it being in the back pocket) just doesn't seem right on any level.
MAN am I glad I saw this thread before wiping my iPhone for sale when I replaced it with a 6+. I am backing up all documents in iCloud to a thumb drive (regularly now...and also then to dropbox) and will do so immediately prior to a phone wipe so that I can restore them to the cloud from the thumb drive.
I agree it's ridiculous that Time Machine doesn't back up iCloud.
One simple solution: Apple should enable a Preference setting to sync a Mac's Documents folder and iCloud. That way everything would exist in the cloud, on the mac, and in Time Machine.
Anyway, good luck recovering your stuff. Glad you had copies of a lot of it elsewhere. What a nightmare...