Child Item

Why does Apple FileProvider force files into the ~/Library folder which is hidden by default?

Sorry if I’ve misunderstood this article but is it true that Apple’s upcoming FileProvider saves files into the ~/Library folder?

If so, could someone help me understand what the advantage is because it’s a mind-numbingly painful idea for many reasons, one being that ~/Library is hidden by default for most people, another is that all my work data is on a separate disk which there is no way I can change.

And is it really the future of Mac cloud storage moving forward?

Any help much appreciated. Cheers, Ben

Find more posts tagged with

Setting Up the Apps

Desktop

Mac

Spam

Insightful

Accepted answers

All comments

Jay

Hi @Ben S.31, thanks for messaging the Community.

Currently, the behavior is the default for File Provider devices to have the Dropbox folder located in the ~/Library/CloudStorage location, and as such is set by the OS itself.

Regarding the permanence of this change for Mac cloud storage, I'd recommend you contact Apple directly on this matter.

If you have any further queries, feel free to message back.

RickCurran

@jay I think @Ben S.31 perhaps has the same question I have which is whether this is the future for Dropbox on Mac backups? Are we going to be forced to use the Apple FileProvider and subsequently have to have our files in the ~/Library folder?

RickCurran

@Ben S.31 Having looked over more of the consequences of switching to the FileProvider version of Dropbox shown on the "Expected changes with Dropbox for macOS on File Provider" page I am definitely going to stay with the regular version for the time being. Asides from the shift to the "~/Library/CloudStorage" folder location there are a few other issues that may be issues for my use of Dropbox, hopefully some of those issues will be resolved going forward, but the shift to the new location is definitely the biggest issue for me.

Jay

Hi @RickCurran, the updated Dropbox for macOS on File Provider experience was developed to adhere to the requirement as set out by Apple and to ensure the best possible experience for our Mac users long into the future.

It is safe to assume that our goal is to have the same experience for all our Mac users, so the rollout will slowly take place to all of them.

RickCurran

@Jay Thanks, the requirement to move the Dropbox folder to "~/Library/CloudStorage" is pretty big change though, one that means I will be reluctant to upgrade the Dropbox client unless I really have to. As @Ben S.31 points out in his original message the "~/Library" folder location is hidden by default so the change from an easily accessible / visible "~/Dropbox" folder in your user account to what is effectively a hidden location is definitely a step backwards.

I do understand that these changes are prompted by requirements that Apple is making of cloud storage providers due to future OS versions deprecating kernel extensions, but the changes are quite significant and the side-effects / consequences are fairly significant. E.g. for users like Ben where they have their Dropbox folder located on an external drive. I don't think it's that uncommon for people to run Dropbox configured that way. With a 2TB Dropbox account and only a 1TB SSD in my Mac I only make it work by only having a particular folder stored locally on my Mac, the rest of the files stay online only, so if I want all my Dropbox folders locally I would need to use an external drive, so this is a pretty significant shortcoming of FileProvider.

As I understand it I don't believe it is possible to use a symlink to connect the Dropbox folder in "~/Library/CloudStorage" to an external drive, can you confirm that this is the case? What will happen for people who need to keep all of their Dropbox files locally and therefore need to use an external drive? Does this mean Dropbox will be unable to support this configuration?

Jay

This thread should help answer your questions regarding the changes of the external drive usage.

RickCurran

@Jay Thanks, I found that thread and had a read through, it doesn't give a definitive answer about external drive support other than Dropbox are looking to support users with that requirement. I did also find this thread which seems to indicate that it might be possible to use a symlink to link the "~/Library/CloudStorage/Dropbox" location to one on an external drive, so perhaps that may be one solution for those who need an external drive.

Jay

Since it's not something official suggested by Dropbox, I couldn't recommend it personally.

RickCurran

@Jay Yep, no worries, I understand it's not an officially endorsed solution 🙂

RHimadiiev

Maybe I misunderstood something but it is possible to use external drives with File Provider https://developer.apple.com/documentation/fileprovider

RickCurran

@RHimadiiev I don't see any reference to external storage in that article, it does refer to "remote storage" but that is referring to the cloud storage provider such as Dropbox etc.

RHimadiiev

Yes, my mistake.

Buy the way, I had a discussion on Apple forum about it and got an interesting reply:

"It was Apple that created this API and restricts it to the boot volume. But it was Google and Dropbox that decided to adopt Apple's new API. They didn't have to.

It's funny. When Apple publishes really useful APIs for things like font management, 3rd party developers categorically refuse to use it. But then Apple come out with an API that will substantially reduce the features that competitors can provide, effectively limiting them to Apple's own iCloud Drive behavior, they can't wait to adopt it. Doesn't make any sense."

And so for me. Why have Google and Dropbox decided to make such change? It only make things worse, no? What are the advantages?

RickCurran

@RHimadiiev I think there were other reasons why Dropbox and other providers had to switch to File Provider, you'd probably need to ask Dropbox specifically though about it, although I think there are more details in some of the other forum threads here asking about this same or similar issues.