You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
Request: All files available offline by default
Moving the Mac to the new File Provider is great - very happy this is finally happening and support on the new M1 is much better. Kudos!
Feature request: Really miss the feature to have Dropbox...
Hi everyone, and thanks for your patience.
We're re-launching the option to choose the default status of synced files in the Dropbox desktop application (in the Preferences > Sync tab) for users of the newer File Provider version.
It should be available to you shortly. If you haven't received it yet, make sure to update your desktop app, and let us know if you have any questions!
... also notable that I have 100+ GB of files not yet downloaded, and the Dropbox icon in the Menu Bar will often show no activity, as though it thinks it is done. Yet the cloud download icons are next to huge numbers of folders, still.
I will re-click the "Make available offline" option in Finder, which tends to kick Dropbox into doing some syncing. But then it will stop as though it thinks it is done again, still with a ton of files not yet downloaded.
That's a bit of a separate bug. If I could just right click "make available offline" and know that Dropbox would keep downloading until everything was local, then great. But since that also doesn't work, I'd much prefer the old global option to make everything local would return.
Seeing this behavior in all the recent builds since the new File Provider version for M1 support came out. Right now on build 146.2.496, but its been going on for weeks like this.
Facing the same problem on MacOS 12.3 (both on an M1 machine and an Intel machine). The option to download all new files by default isn't available anymore in the preferences menu and new files & folders are not downloaded automatically. This has been so for over 6 weeks now and the latest build I'm on v146.3.4795 isn't any different.
This is a huge regression issue. Surprised it's still lingering.
