macOS - NC icon does not show up in Finder

📱 Desktop & mobile clients
, , ,
1

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 32.0.1
  • Operating system and version (e.g., Ubuntu 24.04):
    • macOS Sonoma 14.1
  • PHP version (e.g, 8.3):
    • 8.4
  • Is this the first time you’ve seen this error? (Yes / No):
    • Yes
  • When did this problem seem to first start?
    • on first installation
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • Nextcloud Desktop Client (Version 33.0.2)
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • No

Summary of the issue you are facing:

I am facing a weird issue with the Nextcloud Finder Extension on macOS and i cant figure out the problem. Nextcloud does not show up as a finder location at all. I have already tried the following:

  • Checked Finder Extensions System Settings (and disabled Adobe CC extensions as per a previous report)
  • Provided Nextcloud full disk access
  • reinstalled Nextcloud
  • checked and reinitiated com.nextcloud.desktopclient.FileProviderExt Service

I do not have this problem with any other client, even on the same macOS version, that im trying to install the Nextcloud app on. Is there any way to cleanly remove every Nextcloud property from my system for a complete reinstall or any other ideas regarding my problem? Thanks in advance.

Log entries

I have retrieved the Client Debug Archive, but i am not pasting it since it contains a lot of personal information. If theres a specific line i can search for, please let me know.

2
  1. You want to use the file provider extension, right?
  2. The Nextcloud desktop client was not installed on that macOS before, right (referring to “on first installation”)?
  3. Full disk access does not affect file provider extensions, they run in a sandbox by design since ever.

From my own experience, the file provider framework can be corrupted to such an extend that I had to set up macOS from scratch last summer. But I am working on file provider apps since years now and messing around with file provider domains daily with a high frequency. Especially with the Nextcloud desktop client before version 4 it was easy to corrupt because it did not use UUIds for the domains yet but that is a different story.

With macOS Sonoma 14.4 (my own blog post from back then), the macOS tool fileproviderctl was stripped important functionality, leaving the apps which programmatically manage their associated file provider domains as the only ones left being abled to do so.

Sometimes a simple reboot helped to resolve problems on macOS, especially on macOS 12 and 13 back then. Did you also consider updating to the latest Sonoma release? You are still on macOS Sonoma 14.1. That might also help.

Sometimes the file provider API also leaves developers helpless because something is off in the internals of macOS. I have observed something like that over the years often, too.