We’re Still Here to Help (Even Over the Holidays!) - find out more here.
Forum Discussion
Solved
Mac OS Sequoia is arriving. Is DropBox ready?
Hi everyone, who remembers the chaos that happened last year with the Mac OS Sonoma update and all the issues we had with DropBox? There was a particular version that caused syncing to go haywire. I remember it all too well, as it took us almost a month to figure out how to fix the problem.
What will happen with Mac OS Sequoia? I admit, I'm quite anxious and would appreciate some reassurance from the DropBox team.
Thanks.
There is an update, see https://help.dropbox.com/installs/macos-support-for-expected-changes.
If you still have trouble, disable the firewall. https://9to5mac.com/2024/09/19/security-bite-macos-sequoias-filewall-is-disrupting-security-tools-and-more/ says most users should not enable the firewall:
"Details are sparse at the moment, but a possible source of the issues is Sequoia’s current firewall. This is useful for managing connections on untrusted networks. If you’re an everyday user and not a security nut or part of an enterprise team, your firewall is likely already off. This is the default on Mac, as most users are on trusted networks anyway (Apple’s way of balancing usability and security)."
69 Replies
Replies have been turned off for this discussion
If you're having trouble seeing it connected in Finder, Force Quit Finder so it reboots. I got lucky with doing that.
Nope, does not work..
dropbox.mac.internal.MacError: [Errno -2001] Error Domain=NSFileProviderErrorDomain Code=-2001 "No valid file provider found with identifier ‘com.getdropbox.dropbox.fileprovider/b4e79465-0da5-40ac-bc27-fc55accddebc’." UserInfo={NSLocalizedDescription=No valid file provider found with identifier ‘com.getdropbox.dropbox.fileprovider/b4e79465-0da5-40ac-bc27-fc55accddebc’., NSUnderlyingError=0x600001e14390 {Error Domain=NSFileProviderErrorDomain Code=-2012 "(null)"}}
not working for me ... kept showing connect
but i noticed, if i disable the macos firewall it works ... not that i would ever recommend anyone do ... hopefully that helps with the dev troubleshooting 🙂
On a subsequent reboot it's working, I never saw a request for dropbox to use network services (I did for many other apps - who were written to work inside the new security changes in this OS releaase) it could be firewall related like Jason mentioned above.
Yeah, the answer is no. DropBox missed the memo about testing against the latest OS. I'm getting a different error from others:
"Couldn't start Dropbox. This may be a temporary error. Please restart Dropbox." (remedy does not work)
In their logs it has this:
dropbox.mac.internal.MacError: [Errno 4097] Error Domain=NSCocoaErrorDomain Code=4097 "connection to service named com.apple.FileProvider" UserInfo={NSDebugDescription=connection to service named com.apple.FileProvider}
and a trace through a bunch of python files.
It's the only thing on my system that has failed (that I've noticed) since upgrading to MacOS 15 / Sequoia. Pretty disappointing.
Still no feedback here. Why treat users like this? Isn’t there some form of respect for customers in the US? Isn’t there some kind of customer care? Just let me know if it’s compatible or not, so I can proceed with the upgrade.
To add Dropbox to the Firewall rules and allow incoming connections/usr/libexec/ApplicationFirewall/socketfilterfw --add /Applications/Dropbox.app
