⚠️ Before submitting, please verify the following: ⚠️
Bug description
When the client is notified using notify_push, according to Library/Containers/com.nextcloud.desktopclient.FileProviderExt/Data/Documents/Logs/log.txt it crawls every folder it has ever seen. Instead of only the one affected (or its parent folders).
This might or might not be by design, but it feels like a huge waste of resources.
Steps to reproduce
- Use macOS File Provider extension
- Browse through the folders on macOS a bit (so macOS knows parts of the folder structure on the server)
- Make a change on the server (create/delete a file, etc.)
- Watch log file, the client crawls every folder it has seen.
Expected behavior
When receiving a push event, I'd expect the client to only download the changes of the folder affected (and maybe its parent folders), not the entire tree.
Which files are affected by this bug
any
Operating system
macOS
Which version of the operating system you are running.
macOS 26.6.2
Installation method
Other
Nextcloud Server version
34.0.3
Nextcloud Desktop Client version
34.0.2
Did this occur after an update or on a clean installation?
Minor version update (i.e. 33.0.0 → 33.0.1)
Are you using the Nextcloud Server Encryption module?
No
Are you using an external user-backend?
Nextcloud Server logs
Additional info
No response
Bug description
When the client is notified using notify_push, according to
Library/Containers/com.nextcloud.desktopclient.FileProviderExt/Data/Documents/Logs/log.txtit crawls every folder it has ever seen. Instead of only the one affected (or its parent folders).This might or might not be by design, but it feels like a huge waste of resources.
Steps to reproduce
Expected behavior
When receiving a push event, I'd expect the client to only download the changes of the folder affected (and maybe its parent folders), not the entire tree.
Which files are affected by this bug
any
Operating system
macOS
Which version of the operating system you are running.
macOS 26.6.2
Installation method
Other
Nextcloud Server version
34.0.3
Nextcloud Desktop Client version
34.0.2
Did this occur after an update or on a clean installation?
Minor version update (i.e. 33.0.0 → 33.0.1)
Are you using the Nextcloud Server Encryption module?
No
Are you using an external user-backend?
Nextcloud Server logs
Additional info
No response