Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check 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
- My problem is totally solved. But after it several times it just seem to been solved. Since a few weeks everything is working again
I finally upgraded to Sequoia (15.1) today, on both of my Macs (MacBook Air, 2020, Intel and MacBook Pro, 2023, Apple Silicon). This wasn't a wreckless move, as I had fully backed up my Dropbox to iCloud beforehand, and had a plan to switch over to iCloud if the worst happens.
Spoiler Alert: The upgrades went smoothly. On the MacBook Air, DropBox briefly showed no Finder icons and sync'd cosmetically (tray icon only, but I could add/sync other files so no constant sync'ing was going on). After a reboot and an hour, it was all fine. MacBook Pro upgraded with zero issues... literally not a glitch.
The things I'd checked before (and after) the MacOS upgrade:
* Full Disk Access for DropBox,* Firewall allowing Incoming connections for DropBox
Why did I just steam ahead? Well, I realised that Sequoia has caused *many* issues for software providers... not just DropBox. Look at the other threads on anti-virus software for a start. Apple introduced many upgrade glitches, changes/hiding of firewall rules, not exposing new permissions that apps require, etc. So, yes, DropBox could have offered us more reassurance, but I doubt that they are going to rubber-stamp themselves as "Ready for Sequoia" in the face of so many potential issues that they haven't caused.
My approach was to have a fallback plan, then to work through the issues as I found them. I also waited for the Sequoia 15.1 release (note NOT 15.0.1)
This morning, my Mac Mini Pro arrived, and with the excitement of something new, I had to go through a migration. I preemptively added Dropbox among the Firewall permissions and activated all the usual consents. It worked with Mac OS Sequoia 15.1, so I’d say it’s functioning. But, as usual, the process was a nightmare, and this year, once again, it ends with a big disappointment.
Catch you next year. Cheers, everyone!
2-months have passed, DB customer service is shocking. People around the world just copying-pasting solutions from the manual till they can, then repeat the same BS: the eng. are working on it.
I'm done with this. I'm out!
cloudresthank you for your thread and patience. I think enough is enoughI updated my mac laptop to Sequioa and found my Dropbox jpg files were unreadable from my Dropbox folder in the top toolbar. As a workaround, I select the globe instead of the folder and download my jpg file from the Dropbox cloud account. That seems to work, BUT I hope Dropbox can fix this bug so I can use it as I've done for years.
It seems I have to click on it and then the image updates
It did start working for me again. Today I have that same error. I haven't yet rebooted so maybe some magic will happen there, but I noticed that Dropbox isn't in the list of File Providers under Extensions in system preferences. I believe this error is since a recent update and I suspect the fact that Dropbox is not in the list is the underlying culprit. Seems like your bootstrap should detect when it needs to re-add itself to this list for whatever reason. Dropping the application on top of the file providers list doesn't do anything so the app itself needs to deal with this.
Here's the excerpts (removing my private info) from the log referenced in the generic "couldn't start dropbox" dialog after launching dropbox:
bn.BUILD_KEY: Dropbox
bn.VERSION: 219.4.4463
bn.constants.WINDOWS_SHELL_EXT_VERSION: 77
bn.is_frozen: True
...
Traceback (most recent call last):
File "desktop/dropbox/client/main.py", line 5994, in _setup_root_for_account
File "desktop/dropbox/client/main.py", line 6208, in _get_root_for_account
File "desktop/dropbox/sync_root/helpers.py", line 537, in get_root_for_account
File "desktop/dropbox/foundation/futures/basic.py", line 874, in result
File "../mac_arm64_dropbox_virtual_env/lib/python3.8/threading.py", line 890, in _bootstrap
File "../mac_arm64_dropbox_virtual_env/lib/python3.8/threading.py", line 932, in _bootstrap_inner
File "desktop/dropbox/db_thread.py", line 96, in run
File "<string>", line 1, in _x__db_thread__sleep_thread
File "desktop/dropbox/db_thread.py", line 36, in set_name_and_run
File "../mac_arm64_dropbox_virtual_env/lib/python3.8/threading.py", line 870, in run
File "desktop/dropbox/foundation/runtime/__init__.py", line 676, in decorated
File "desktop/dropbox/foundation/futures/sleep/__init__.py", line 163, in _run
File "desktop/dropbox/foundation/futures/basic.py", line 704, in set_result
File "desktop/dropbox/foundation/futures/basic.py", line 667, in _on_post
File "desktop/dropbox/foundation/futures/basic.py", line 1050, in _stage1
File "desktop/dropbox/foundation/futures/basic.py", line 421, in _then_callback
File "desktop/dropbox/foundation/futures/helpers.py", line 436, in <lambda>
File "desktop/dropbox/sync_root/handlers/macos/file_provider.py", line 1043, in _get_mount_path
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}- Jay
Dropbox Community Moderator
Hi zmre, thanks for the info. In order to look into this matter in more detail, I'd recommend contacting the support team directly for them to investigate further.
