What is really going to happen with CloudStorage?

[g v.]

Hi, 

Luckily, my Dropbox folder is still in my home folder. I have Dropbox 179.4.4985 . Selective Sync and Smart Sync are completely off, all new files are on my hard drive by default. I'd like to keep it that way. 

Is it possible to just not install this Dropbox update that will move my Dropbox folder?

Can I upgrade to Ventura 13.5 without having to update to a Dropbox version that moves my home folder? 

Please inform neutrally. I'm not angry, I just want to make a decision that works for me. 

Thanks

[Calvin2DBX]

Hi @g v.,

Just chiming in here to help you better prepare for what's been discussed.

To recap, as my colleagues confirmed, any OS higher than 12.5 will see the app ask to update, eventually, since this is a requirement by Apple moving forwards with File Provider.

For now, there is only an option to start the migration, when you are ready. If the migration has not happened for you, leave it as it is (it doesn't do it automatically, so there's no postpone option.)

The only other thing I would add, if you are concerned about accidentally clicking yes to the update, is to sign out from the app. That way, you can be 100% certain that nothing in your existing Dropbox folder structure can change at all for now. However, keep in mind that while signed out, the files won't sync to the web or other devices. You can sign back in when you're ready.

I hope that helps!

[crimsonnoise]

Hi Calvin and Jay,

I am currently on MacOS 11.7.10 and my Dropbox folder is on an external drive, and it will have to stay on an external drive.

If I now upgrade to MacOS 13 or 14, I will presumably be required to update the Dropbox app - but can it update without using File Provider, so the Dropbox folder can stay on the external drive?

[Hannah]

Hey @crimsonnoise, you should be able to find an answer to your query here.

I hope this helps.

[crimsonnoise]

Thanks Hannah. I had looked through that, but I wasn't clear about the implications.

Does this mean that when I already use Dropbox on an external drive, and then upgrade to let's say MacOS 10.14, I can keep it on the external drive, or will the new MacOS require the use of File Provider?

Also the last paragraph in that article "Using external drives with Dropbox for macOS on File Provider": So with this method is it possible to override the File Provider's ban on moving the Dropbox folder to an external drive? 

[Hannah]

Thanks for getting back to me, @crimsonnoise.

Just to clarify, since the majority of external drive users aren’t eligible to migrate to Dropbox for macOS on File Provider, it's not certain that you will be one of those who are eligible.

You can update to File Provider on your OS, but you might or might not receive the notification to update your Dropbox as well.

If you do get the notification and choose to update your Dropbox to the File Provider version, the way to basically "undo" that, is the steps in the article I linked above.

I hope this clarifies!

[HagamLO]

Hello everyone!

With my great delight, the small design company I work for decided to migrate from the awful OneDrive to Dropbox for Mac. While helping the owner test the new setup, I saw in setting that we're currently on the NON-FP version of the app.

While I understand that the old version was objectively better than the File Provider version, I'm wondering if it would be smart to force installation of the File Provider version to the entire team, rather than having them upgrade to FP down the line when the change is enforced for everyone. This article outlining the differences, notes that "While we recommend opting-in to the latest version of Dropbox for macOS on File Provider, this migration isn’t required for you to continue using Dropbox."

How long is the migration NOT going to be required? Is there an official timeline? Can we expect to use the NON-FP version of Dropbox for years to come, or is the migration going to be enforced in the near future?

Thank you very much

Edit: did I completely botch posting a new thread, or was my query merged with an almost-unrelated question?