why is iCloud drive not showing all my folders?

You can only create nested folders (that are functional) outside of the iWork apps' folders. If you try to make one within, they wil not show up on icloud.com iWork apps or iOS iWork apps.

That's what you asked, a nested folder, in an iWorks app folder that was functional and accessible on all 3 platforms. And that is what I replied to.

I appreciate your reply, but I must not have been clear. I would like there to be a third level of nested folders/sub folders. For example, I can create a folder within the Pages folder on iCloud Drive called "Work." That is great. However, I then want to create a sub-folder within this folder for various work projects, and possibly other folders within those. This would be similar to what you have done in your 'personal' folder. Does that make sense? Again, if this possible please let me know.

I don't actually use the app folders at all, I file things by project rather than app. So I just copied an existing folder tree to use. It does seem that 2 deep is all you get in the existing app folders, but why use the old app centric (aka useless) method when a better one is available?

I use those folders because they are the only one's that reliably sync for me. For instance, I just created a folder outside the Pages folder on icloud.com and it has yet to be available on my phone via the Pages iOS app.

There is no sync, there is just one iCloud drive with files on it, the phone and everything else read from the same drive. You can access any part of the iCloud drive from the root down to the lowest subfolder.

Right, but maybe there is a problem with my phone then because folders created outside of the app-centric ones do not reliably show up on on my phone via the document picker you're showing. However, that folder will be available on my Mac, iCloud.com, and even on iCloud Drive on my work PC.

I guess that is possible, for me any folder shows up everywhere, no noticeable delays.

Hi guys

I Had tried many different solutions /suggestions in this forum, including turn off FileVault, kill bird & cloudd in activity monitor, sign out & sign in Icloud.com....etc

nothing works for me.

it is so time-consuming & so I quitted

I ended up with buying a USB flash drive to continue with my work / project and save it to Dropbox for long-term use.

Frankly speaking, I am a big fan in Mac but this time, it really disappointed me. (Another App that is really disappointing is Map when it was released)

DRopbox is really simple & ease of use.

good luck to all of you guys.

After installing the update available today 11/17/14 Version 10.10.1 my issue stated above has been fixed.

I disabled and enabled iCloud drive in my iphone settings. Now my scanbot folder is showing up. I think it only shows folders which have files in it. Others it hides. Stupid if you ask me.

"So iCloud drive is definately creating a local copy..."

This is not exclusive to iCloud Drive. My experience is that ALL of the cloud-based connectors -- i.e., OneDrive, Dropbox, Box -- are actually taking up local space on your HDD as well as in the cloud. I had the same issue when I connected my OneDrive folder. I was wondering why I went from a little over 300GB space to almost nothing after it synced. I thought the whole purpose was to keep the stuff in the cloud but I suppose it has to work this way, which, I agree, is pretty useless but it's the reality of cloud-based workflows and their desktop companions.

I also see the same pattern that others are seeing here: iCloud Drive from iCloud.com shows a bunch of folders but in Finder those same folders don't appear unless they're something in the folder. I saw a Quicktime folder on iCloud.com but nothing in Finder. Once I moved a file into the website it showed up locally in Finder.

I'm actually considering biting the bullet and just paying the extra $10 a month for 1TB from iCloud than Dropbox that's been syncing for over 3 days and still isn't done. Granted I probably have about 20GB or so of data trying to sync locally from the cloud but that shouldn't take that long (and it's actually still not done, which means it could be another day or more to complete).

I have a connection with download speeds exceeding 100Mbps and uploads at about 12Mbps. Not the best going up but I don't understand why Dropbox is so friggin slow.

But I digress.

I don't know the answer to the cloud vs. local drive issue. I do think it's frustrating to be forced to keep a local copy of the file that's also in the cloud but if you really think about it using bandwidth every time you want to view a picture, document or video file would quickly max out your allotted monthly bandwidth.

I agree.

This "cloud" stuff is half-baked at the moment, as no one really knows what to use it for, or more importantly, HOW to use it (from a technical perspective)...

- Should we be storing ALL our personal files (and file structure) up there yet, or just the essential things?

- Can they handle even 1TB nevermind the multi-TB's of data many users have, yet?

- When on desktops (e.g. Macs/PC's), should we always have cloud AND local copies, or can we offload some to cloud only?

- When on mobile devices (eg. iPads/iPhones), what then; how should one attempt to manage files?

- Sync: how should users expect it to work?

- What are the SPECIFICATIONS for these cloud providers? (e.g. nested folders are dealt with how? How deep can folder structure be? etc.) --> you'll never find this kind of thing listed with Apple's services, it's such a joke we have to essentially guess what might or might not be possible!

...yadda yadda etc. etc. and loads of other questions unanswered...

I personally think they're mostly fluffy extras to make the companies look like they're offering some sort of "cloud" storage, rather than being anything substantial for the average consumer to get their head around using properly at the moment.

I tried to get a spec for iCloud email functionality the other day, but guess what; there ISN'T ONE! (Applecare don't have one either BTW.) That pretty much sums-up Apple's philosophy when it comes to services rather than physical products, with Macs and iOS devices having their full specs published properly, yet iCloud's multifaceted functions have most specs unpublished, seemingly very deliberately by Apple.

" So iCloud drive is definately creating a local copy..."

That is because you are using a cloud service that's keeping your files in sync. Dropbox, iCloud Drive etc. are watching their native folders (or the one you specified) 24/7 and whenever you copy a file into one of these watched folders or create/save a new file within them, they are synced to the Cloud. The reason for this is because these Cloud services are meant to make your files accessible on all your devices via the internet. So whenever you copy something into the cloud that is outside of the local watched folder, it'll be copied into it (actually it will be re-downloaded from the cloud).

This is what Dropbox, iCloud Drive etc. have in mind: They want you to use their native folders for your files. That way everything is always in sync.

This is what some of you are looking for: An online Backup (2nd copy) of the files without a local synced copy. You can do this by uploading your files to a FTP server.

This is how I use Dropbox and iCloud Drive: As long as I need some files available on all devices, I have them within the local folders of the cloud service. When I am done editing them I move these files from the local cloud folders into my own folder hierarchy outside the local cloud folders. Of course this will also sync and remove these files from the online storage.

So yeah, the only way to work comfortable with synced storage is to work completely inside of its folders.

But what happens if the "sync" function fails; what then?

And how do you even check the data integrity of your file system, to make sure corruption of the data hasn't occurred, and/or all your file history have/haven't synced properly onto the server? You can't AFAICT.

Even if only some of your files disappear from the cloud, thus sync has failed, unless you realise it's happened, you're none the wiser. On TB's of data, there's only so much incremental backup you can afford to have and deal with; both in cost terms and (more importantly) in terms of time/effort/bother.

No word from Apple on how we or they deal with such issues. Thus = fail, from a trusting for anything but the most basic of uses perspective.

I think Dropbox at least allows you to pay for "unlimited recoverable file history" (or something?) for a kind-of permanent incremental backup of sorts. But Apple has no such efforts, at least none the users can see/use, and certainly none they've made public. Typical Apple behaviour when it comes to their services; half-baked, half-hearted, with "hidden" detailed specifications users cannot see. It makes one believe they don't even trust it works effectively themselves, if they don't release clear guidelines for usage.

e.g. (classic longterm iCloud issue this one) empty folders don't show on some devices, for reasons unknown but to Apple?!

Same here!!!