Anyone else seeing the agent crashing or stopping on MacOS 26.x? I have a new setup running on both MacOS 15.7.3 and 26.2 and my agent on 26.2 keeps crashing or closing. Any thoughts or recommendations on how to keep it running?
Hi! Do you mean the macOS desktop client?
Yes. The one that syncs files between my NextCloud instance and other endpoints running the app.
Are you using the classic folder synchronization or the virtual file system also known as file provider extension?
Usually, the client works fine on those macOS releases. Did you install it freshly and without any leftover account configuration from previous installations? What client version are you using?
What does the crash report state?
I also experience really bad results with the desktop client on macOS nowadays.
The VFS uploads files but they are not downloaded on other machines.
The classic version doesn’t show the Finder contextual menus, so no access to the sharing options.
It’s just became terrible.
Macos and desktop are latest versions.
NB : There are up to 3 accounts configured on the VFS version.
I am using the latest VFS version and it is a new install on all my Macs as I am testing this out as a possible replacement to Synology Drive Sync. The files sync fine while the agent is running, but if I don’t use my Mac for a while or lock and unlock it after 6-8 hours, the agent is no longer active in the menu bar and I have to re-launch it.
I am new to NextCloud, where can I find the crash report? I can take a look at that as well.
A fundamental change and fix in the remote discovery will be delivered with our next release.
You cannot enable classic synchronization and file provider extension simultaneously, see client user manual. This is a limitation imposed by macOS we cannot overcome.
On macOS, open the “Console” app. In the sidebar, there is the “crash reports” item. When selecting it, you maybe see a list of crash reports in the content area of the window (if nothing crashed, then there are no reports). Do you see any named “Nextcloud” or “FileProviderExt”?
1 Like
Thanks @iva.horn !
Makes sense. The user should be warned about this when he enables both syncs. Additionally, I guess that this is true once you enable the file provider extension for any of the configured accounts ?
Something else : the share options doesn’t show up when the nextcloud instance is configured with ldap authentication. I believe I found the bug but there is no activity / answer on this issue : Incorrect WebDAV Path Used in File Provider Share Management · Issue #9074 · nextcloud/desktop · GitHub , could you have a look ?
Yes, this is an app-level limitation.
Oh, thank you for pointing that issue out. I missed it. I assigned myself and subscribed so I do not loose it but I cannot state when this will be tackled.