The Nextcloud desktop team has published version 35.0.1 of the desktop client, a maintenance release that backports a broad set of fixes to the stable 35.0 branch. The changes were collected through the project's backport bot, so this is a consolidation release rather than a feature milestone. The release notes are available on the GitHub release page.
What changed
Several themes run through the changelog:
- File provider work, especially on macOS: avoiding a cleared download state after a failed materialized enumeration, keeping shared files writable under their own lock, building XPC components with ARC, correcting sharing dialog fields, restricting the File Provider Keychain scope, and declaring
NSLocalNetworkUsageDescriptionfor the File Provider extensions. - Windows virtual file system handling, with two backports aimed at making the VFS more reliable and improving new-folder handling.
- Sync and network behavior: request timeouts are enabled again, change delivery acknowledgements are made safe against late and concurrent requests, and duplicate or slow sync error entries in the activity view are avoided.
- Desktop integration: QML dialogs and windows can be closed with the standard window-closing shortcuts, Qt submenus in the tray stay attached to their parent, and the AppImage resolves its installed icon from the desktop entry.
- Database and watcher fixes: inode values are now guaranteed unique by adding an index, and the folder watcher no longer follows directory symlinks and junctions.
- Setup wizard and branding: the sign-up button can be customized or hidden, branding can hide the Self-host button, and
overrideServerUrlandoverrideLocalDircan be resolved via managed settings. - Packaging and CI: the Flatpak package gets a corrected icon name, macOS tests now cover multiple native components, and CI uses KDE's GitHub mirror of craftmaster.
Who is affected
Anyone running the 35.0 desktop client, particularly on macOS and Windows where most of the file provider and VFS fixes land. Administrators who brand the client or preconfigure server settings through managed settings will also see relevant changes.
Why it matters
Desktop sync is the part of a self-hosted Nextcloud setup users touch every day, and small reliability issues there turn into support tickets. This release tightens error handling, network behavior and platform integration without changing how the client works, which makes it a sensible update for existing 35.0 installs.
Commentary for self-hosters
Treat 35.0.1 as a routine maintenance update: test it on one workstation per platform before rolling it out widely, and pay attention to macOS machines that rely on the file provider and to Windows machines using the virtual file system. If you ship a branded client, check that your sign-up and Self-host button settings still behave as intended after the wizard changes. If you build on Nextcloud for your users, our Nextcloud apps are a good place to see what else you can add to your instance.