We’re Still Here to Help (Even Over the Holidays!) - find out more here.
Forum Discussion
Solved
Spotlight Search Doesn't Link to Files in Dropbox in macOS 13 Ventura
After upgrading to macOS Ventura, I was prompted to upgrade to "Dropbox for macOS 12". I proceeded with that, it moved my Dropbox folder to ~/Library/CloudStorage and confirmed all was successful. Now when using Spotlight to search (I often type something like 'drawings folder' to open a folder called Drawings) the results in Spotlight show the Dropbox app icon beside the name of the item I want (rather than a Finder icon for folder or file). Hitting Enter or clicking on the result switches to Finder and does nothing, or sometimes will open the Applications folder and show the Dropbox app. It's not linking me to the actual file in ~/Library/CloudStorage.
I have done the following and the problem is not solved:
- Restarted
- Ensured all files are available for offline access
- Rebuilt the spotlight index
- Unlinked Dropbox from this Mac, did a complete clean install of dropbox, performed the upgrade to v159.4.5870 and synced just one folder to begin
Nothing works. Any suggestions??
- That’s the same problem I had. I solved it by doing a complete clean install of dropbox. You may not need to do all of this, but to be safe, in Dropbox settings Selective Sync uncheck all of your folders and wait for them to be removed from your Mac. Once that’s done, unlink your Mac from Dropbox preferences. You should see the Dropbox getting started screen. Quit Dropbox and move the app to the Trash. Remove all dropbox files from ~/Library being careful to look at the path name. Only remove things that are within a Dropbox parent folder. Look in library application support, and library preferences. Empty the Trash. Restart your Mac. Reinstall Dropbox from dropbox.com. Once reinstalled, to make things faster sync only one small folder and wait for the prompt that new Dropbox for macOS 12 is available. You should see the message within a few minutes of reinstalling Dropbox. Allow it to upgrade and migrate your files to the new location. Once that’s done you can then sync all your folders. Let your Mac index itself and the problem should be solved.
398 Replies
Replies have been turned off for this discussion
Like everybody here, I cant use spotlight anymore with my dropbox, and it's killing me. Same, 10 years with Dropbox, and now I have to reconsider my all company organization because of that shi... update. What the hell Dropbox???? Please do something!!!!! Move the file out of "library/cloudstorage", go back to the previous system!!!
- Guess what! Even if you revert to dropbox being in the system folder, on an M2 mac and latest OS (and the latest pre move dropbox) the piece of junk still won’t allow “within folder” searches. It will still only index at the mac HD level, making it less than useless.
Both Apple and Dropbox are to blame and I suspect dropbox don’t give a **bleep**. Apple should as it’s their problem to fix as their $5K M2 is now no better than a fast ipad to me without easy file navigation
Perhaps Apple is trying to force icloud usage and if so should be fined by federal authorities and EU. We need to post wider on these issues until they take note. Spotlight worked perfectly on a M1 pro before this **bleep**ty update. So there must be a solution. They just have to undo what they did for this update.
https://help.dropbox.com/fr-fr/installs/macos-support-for-expected-changesYes, I agree, I also have an 13" M1 and I have not updated it - and it still works fine.
What is a disgrace is the bs advice the dropbox staff are giving out - knowning full well it does not solve the problem - so many must have complained by now and yet they still have us deleting db and. reinstalling and re-downloading terabytes of data and then re-indexing over a day or two to find we are back EXACTLY where we started.
Mean while my main work computer is about as useful as a wet fish.....
Is there any way to install an older dropbox version again to avoid that? Anyone with an old .dmg ? Someone tried that option already?
Not managed that I'm afraid. I now have drop box v172.4.7555 back outside the cloud OS folder - i.e. back in the old location but that still does not make it operate as on an M1 or an Intel Mac. I have not tried to roll it back further. Already lost 3 days of work use of the M2 due to dropbox staff "experts".
I am assuming that without admitting liability they will release an upgrade in the coming months that solves the problem. They are an unethical company.
FrenchJack, you can find all the older stable builds here. I have upgraded to the latest version but not opted to have Dropbox move files into the /CloudStorage location, which seems to be working fine for me. I know some people have said that on MacOS 13.3.1, the /CloudStorage indexing works fine, but there are enough people here who are still struggling with getting it to work, so I've just left my files in the original /Dropbox location.
JoePL We have to be careful defining 'working fine' - can you go into a subfolder in dropbox and search for relevant files only in that subfolder? Thats the specific problem I'm seeing and its not related to indexing per se - thats working fine in that the entire HD can be searched for the relevant files (although thats useless for my work.... )
"@jat1971, was it not indexing for you in the /CloudStorage location? Curious if you were still experiencing the problem with MacOS 13.3.1? Some users have claimed upgrading to MacOS 13.3 fixes the /CloudStorage indexing issue, but some people seem to still be having the issue. "
The mac OS is indexing in both the /cloudstorage location and once db was moved back to its traditional location. Indexing isn't the issue. The issue occured on 13.2 and 13.3.1 (that idea that this fixes the issue was nonsense the db people told me).
Its the spotlight functionality within the dropbox folder structure that is lost. I can't pick a specific folder and search within that folder only. 3TB of files, lots of hits per search - needs to be targeted for me... and through work spent months of time providing that structure.
The db people have absolutely no liability for the nonsense advice they give out. Other than "have you tried to restart it" every other piece of advice didn't work but did cause major disruption without any upside.
I am assuming that a new update of db and/or Os will solve the problem - and no liability admitted.
