Client Automatically Syncs New Files and Folders
- Dominant language
- C++
- Stars
- 3.9k
- Forks
- 1k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 127
Description
### ⚠️ Before submitting, please verify the following: ⚠️
- [x] This is a **bug**, not a question or a configuration issue.
- [x] This issue is **not** already reported on Github (I have searched for it).
- [x] Nextcloud Server and Desktop Client are **up to date**. See [Server Maintenance and Release Schedule](https://github.com/nextcloud/server/wiki/Maintenance-and-Release-Schedule) and [Desktop Releases](https://nextcloud.com/install/#install-clients) for supported versions.
- [x] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/)
### Bug description
The client starts syncing new folders on itself and there does not seem to be a toggle to disable this behavior.
### Steps to reproduce
1. Choose folders to sync
2. Create new folder on the server
3. The client immediately starts syncing this folder.
### Expected behavior
Do not do that. When I choose which folders to sync, I deliberately do that.
### Which files are affected by this bug
?
### Operating system
Linux
### Which version of the operating system you are running.
Fedora Linux 44 KDE
### Installation method
Distro package manager
### Nextcloud Server version
Nextcloud Hub 26 Spring (34.0.3)
### Nextcloud Desktop Client version
34.0.2
### Did this occur after an update or on a clean installation?
I don't know.
### Are you using the Nextcloud Server Encryption module?
No
### Are you using an external user-backend?
- [x] Default internal user-backend
- [ ] LDAP or Active Directory
- [ ] SSO - SAML
- [ ] Other
### Additional info
The client apparently also did non bother about the toggle "Ask for confirmation before synchronizing new folders larger than: 500 MB (default)" and happily synced a new 11 GB folder on it's own.
Contributor guide
Research direction
Reproduce the issue using the listed folder-selection steps on the Nextcloud Desktop Client, including a newly created 11 GB server folder. No affected files or tests are identified, so first locate the folder-selection and new-folder confirmation behavior. Done means newly created folders do not sync unless selected and the configured confirmation threshold is respected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100