Q: iCloud Drive not syncing locally

I've done my investigation, whatever that means.

I've concluded that the issue is in the cloud daemon [cloudd]. Bird is downloading the files correctly (albeit slowly) and the data is streaming through, but the issue is that there are completed files in '~/Library/Application\ Support/CloudDocs/session/p/[file name]/p' in correct form. If you just copy the folder out and rename it [x].pages, then you get a working file.

Coupled with an analysis of the iCloud sync logs in Console's '/var/log' folder (heading, 'com.apple.clouddocs.asl'), bird has finished its downloading. The trouble is translating the finished files into an actual product — in the iCloud folder. Quite unfortunately, it has been impossible to move this data. Right now (2:04:57 EST), I'm trying to kill cloudd multiple times to see if it does any good. Considering cmaus's comment earlier, I have to object to saying that iCloud is not downloading the information. I would say instead that it is being downloaded, just the data is not reaching '~/Library/Mobile Documents/com~apple~pages/'.

In the end, I don't see a solution to the problem. Simply put, there isn't a manual way to get cloudd to work effectively. I know of no command line tricks regarding it nor any GUI tricks. Furthermore, annoyingly, this bug is still so new that there are no treads except this one talking about the errors.

About those errors, is anyone else getting any of these?

• Item isn't staged yet: r:712 i:com.apple.Pages:00000000-0000-3000-0014-000000000BC6 up:idle st{p:00000000-0000-3000-000E-0000000054EE n:"[document.pages]" doc reserved etag:6p3 bt:1396452328 m:rwx hidden-ext pino:45856823}
• Assertion failed: dv
• cloudd[PID]: Failed to authorize putting assets ("<CKDMMCSItem: 0x7fc6cc8b30f0; itemID=19499, size=253, recordKey=pkgContent, path=\"/Users/[moi]/Library/Caches/CloudKit/tmp/F88E9D03-44D2-462A-9D52-1A5071D 44AEC\", signature=<013a6ee4 f9ade4a3 187cdfab fba81aa2 1a09aa1a ab>>", "<CKDMMCSItem: 0x7fc6ccaea030; itemID=0, size=1631906, recordKey=pkgContent, signature=<0271747b 9f56bc0e 4ac4532a f25a5ddb 3ee4557c ea>>") for package <CKPackage: 0x7fc6cca9aed0; itemIndex=7, recordKey=pkgContent, ownsTheAnchor=NO, anchor="/Users/[moi]/Library/Application Support/CloudDocs/session/u/3L68KQB4HG.com.readdle.Scanner_0AEBA5AC-C1D1-49D8-9 2AA-7CC806D43E51/ckpackage", path="/Users/[moi]/Library/Caches/CloudKit/com.apple.bird/790255cf9f58beaaa5fa7 4ca5c8227329b982cc8/Packages/E2222046-3698-4315-AE15-A9FDF9D320B1">: <CKError 0x7fc6cc8df900: "Internal Error" (1)>
• cloudd[PID]: Received error 16 from the server [...] type = atomicFailure

Note that the first two comes from com.apple.clouddocs.asl and the latter two come from the System log (search for all instances of cloudd).

[Continuing from the last post]

I believe I've found a solution—clearing all of the files on iCloud and re-uploading them.

Since I keep backups for everything I write, this was not too much of a hassle. You can find the backups if you have a time machine capsule inside ~/Library/Mobile\ Documents/com~apple~Pages/Documents/. It may also be prescient (if you don't have extensive backups) to download the files from iCloud and then to put them on hard disc whilst you clear out the Pages library.

BACK UP YOUR FILES TO HARD DISC BEFORE DELETING FROM iCLOUD

To delete the files, go to >System Preferences>iCloud>Manage. Select (for me, it was) Pages and delete all files on the cloud. After sending the command, trigger a full update by restarting your computer. For me, it started working again. I presume it was something wrong with the files. I'm confident that if you have a large number of backups, you should be able to piece together all your files again.

I think the error may have something to do with the old Pages '09 files (.pages-tek, i think) or files which throw an error as not being 'staged'. Not sure where the problem comes up, but a full reset on the cloud side seems to work. The changes may take some time to show up on your phone. I used a hard reset to try to clear any errors there (hold the home button and the sleep/wake button for about 15 seconds). I hope that this solves your problem.

When I called Apple, they said they knew of the issue and that people had called within the last week complaining of the same thing. Call. It'll motivate them to have it fixed. Systematic errors cannot be ignored.

This may be very idiosyncratic but it has worked for me (so far) and may help someone else. Everything was working fine except the iCoud drive local folders on a Mac using Yosemite didn't update. I logged out of and back into iCloud and everything was updated. However, subsequent  changes made from the iPad were not reflected. It turns out the changed files were in a folder. I created a new Pages file at the top level of the Pages folder from Safari at iCloud.com and not only did that file synch with iCloud drive, but the files within a folder snched too. I don't know if this will continue to work.

Kind of funny iCloud Drive works perfectly on my Windows 7 Laptop, but on my new 2014 Mac mini..nope. Not a very good first impression Apple is making on a first time Mac user.

You can always tell when Apple has screwed the pooch: nobody from Apple, or any of the Forum apologists with thousands of posts, has anything to say on threads like this. iCloud Drive doesn't work and it's not because of site traffic, or transient problems, or operator error.

I tried repairing permissions on my startup disk, and killing cloudd and bird from activity monitor. After I restarted, folders magically started showing up in my iCloud Drive folder in Finder!

After having this problem since iOS 8 /iCloud Drive was released, I found that the solution proposed by kevinifly6 worked for me. It seems like it is older types of files, perhaps from previous iterations of Pages, that are "clogging up" the system. So going to >System Preferences>iCloud>Manage. Select Pages (and/or Numbers, or Keynote) did it for me.

Note that I unfortunately didn't have the intricate backup system that kevinifly6 had, so first I went through the time-consuming process of downloading ALL my Pages files from iCloud.com. It was time-consuming because many of these files (I have about 500 in there) would at first download only unreadable files (those ending in .pages-tef when downloaded). For those, I had to go back and open them in iCloud.com and in some cases make a small change to get them to 'update' in the cloud. After that, the vast majority would download correctly. There were a couple files that I could no longer correctly download or open in ANY form, but this happened with only a very select few.

After downloading all my files and making sure they weren't unopenable .pages-tef files, I did the resetting of files described above. Files immediately disappeared in Pages across my devices and in iCloud.com. I then started re-adding the hundreds of downloaded Pages files back in, and they fortunately began appearing and working across my devices again!

Note that I had previously tried ALL other ways I know of to reset iWork/iCloud Drive and none of the worked. This included deleting and redownloading all iWork apps across iOS and Mac devices; turning iCloud Drive off and on, turning each iWork application off and on in iCloud Drive, resetting all settings on iOS devices; and even deleting all documents from within iCloud.com (a good chunk of them gave me an 'error' message that the server couldn't be contacted and then the deleted documents just reappeared). In other words is the ONLY thing that worked for me was >System Preferences>iCloud>Manage

This isn't to say that all problems have been solved, as documents still often decide to upload or download slowly at random times, and I still get too many freezes of all the iWork apps on iOS devices. But it's a **** of a lot better than what it was, and at least I can now semi-reliably work on iWork documents across my multiple Macs and iOS devices. I can't believe Apple has so utterly failed at all of this.

Hi

I have solved one of my issues with this.  A folder I created was not updating on my Mac.  When I looked at "Get Info" on the file and looked at permissions, it was marked as READ ONLY.  As soon as I changed it to not be "READ AND WRITE" it updated.  Try it.

Todd

I have the same problem with OS X not syncing with iCloud. iPhone and iPad work fine. The specific errors I get in the console are:

bird: zone creation error: <CKError 0x7fea6126b2b0: "Partial Failure" (2/1011); "Failed to modify some record zones"; partial errors: {

  com.apple.TextEdit:__defaultOwner__ = <CKError 0x7fea6125a360: "Network Failure" (4/-1); "unknown error">

}>

cloudd: Error fetching database URL from the server: Error Domain=NSURLErrorDomain Code=-1 "unknown error" UserInfo=0x7f8cc2d6dd50 {NSErrorFailingURLKey=https://setup.icloud.com/setup/ck/v1/ckAppInit?container=com.apple.clouddocs, NSLocalizedDescription=unknown error, NSErrorFailingURLStringKey=https://setup.icloud.com/setup/ck/v1/ckAppInit?container=com.apple.clouddocs}

I've tried the workarounds posted so far. I've tried signing in and out of my account multiple times. Multiple reboots. Different networks. Nothing works.

I've also tried signing in with another apple ID and found that syncing does not work with that account either, even though it is working fine on another machine.

I've tried creating a new user account on my machine and signing in with my apple ID and it does work over there. So there is obviously something wrong with my primary account. I've cleared out a heap of preferences and caches and tried copying things from the good account, but nothing is working. I'd prefer to not setup a brand new account, but that's looking like the best option at the moment.

In my case, the problem was that I was using iRamDisk to create the User Cache in a Ram Disk. When I switched to another account, I was using a normal user cache and it therefore worked. Once I figured that out and deleted the Ram disk I was using for user cache, my icloud drive started working properly.

I am *possibly* about to make your day. I hope so anyway!

I had the exact same problem - tried all the stuff you had, signing out of iCloud, signing in again. Nothing worked. My iCloud Drive was half stuck, with only some files actually being shown, and none accessible.

Console showed loads of errors in file writes. I made a new Administrator user account and found I could sign in to that on iCloud and iCloud drive worked fine!

After removing any Keychain iCloud related entries I was still no closer to a fix. I even dumped all my Apple preferences to no avail. Then I looked at the Console and noticed that most of the errors seemed to relate to the sandbox refusing the cloudd process to write to disk.

Then by comparing various folders in Library between a virgin non-iCloud signed-in account with what happened to these folders when iCloud was signed in I found the following folders were created in ~/Library/Containers as a result of signing in and switching on iCloud Drive:

com.apple.DataDetectorsDynamicData

com.apple.internetaccounts

com.apple.CloudPhotosConfiguration

com.apple.notes

Looking inside com.apple.internetaccounts the container.plist file contained a great big entry entitled SandboxProfileData. Aha! Could this be the thing that Sandbox was complaining about, thus not letting the iCloud Drives files be created on the hard drive?

Anyway - I signed out of iCloud completely in my account, waited a minute, deleted these 4 folders, restarted the iMac and signed in to iCloud.

Lo and behold, iCloud Drive now works beautifully!

Hope this helps ...

For the non-techie amongst you, you get the ~/Library/Containers folder by opening Finder, and whilst holding down the ALT key click on "Go" on the top menu and you'll see "Library" - click on that. Inside you'll see the Containers folder.

That did the trick for me, thanks a lot!

Nope did not work for me. It does work mind you. A file of a wopping 500KB did fully download (in a couple of hours). The rest is still downloading incredibly slowly. Not even close to anything I can just download normally over my internet connection. I don't mind that Apple gives no feedback whatsoever for diagnostics (like what iCloud Drive is doing in the background - KB / sec for example, which file it is downloading etc) but then it should simply work....

I give up (again) and wait for Apple to fix (or at least acknowledge it is an issue in the first case)....

Great, putting the old ...CloudsDocs into the trash creates a new one and seems to fix the issue (I hope everything is still there after restarting).

Solved various synchronizations issues with a number of (all?) apps on my iPad and iPhone. I used "notes" to check ync performance creating new files on the differnt devices (including iCloud Notes on the web). NO GURANTEE THAT IT WORKS ALWAYS AS YOU WISH, TRY AT YOUR OWN RISK ONLY AFTER SYSTEM BACKUP.

BTW: I found some similar issue with iPhoto when I was trying to install the new iPhoto. It kept asking me for downloading the update. The I deleted an old iPhoto folder in ~/Library/Application Support and suddently the new iPhoto started asking for an app to convert the old iP7 db to iP8 which I downloaded and ran - took 30+ minutes.

Who did this? This is lousy and not at all like Apple style user comfort.

Had similar symptoms on my mac mini when I realized that my user Library folder was locked.

Don't know how this happened.

Maybe because I used to be a Mac OS beta tester.

Unlocked it and iCloud drive is working.