-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Constant sync issues since upgrading to latest version (23.0.1) #30948
Comments
I can confirm this issue. Nextcloud 23.0.1 with PHP 8.0 on Ubuntu 20.04 with Client 3.4.1. I noticed it because I synced my Notepad++ settings and open files and every time I hit enter my client notified me of conflicts. |
Downgrade client to 3.3.6 |
hahaha you can't be serious.🤦🏼♂️ |
|
Meaning no virtual file support? :( |
3.3.6 support virtual files as well. |
Oh, good to know. Thank you. I'll try downgrading. |
seems to me they have lost control of their software. |
Strike that, it came back. |
did you all upgrade from 23.0.0 or from 22.2.3 ? |
I've upgraded from 23.0.0.
This does work. Make sure to remove the new version before installing the old. |
Closing as duplicate then nextcloud/desktop#4141 |
Bug description
I usually work in VS Code (Windows 10) and have one of my Nextcloud folders open. Since I updated Nextcloud Server to v23.0.1 yesterday, I get a sync conflict after every other save. I'm forced to choose to save either the local copy (latest) or the server copy (older).
Steps to reproduce
Expected behavior
No sync conflict
Installation method
Manual installation
Operating system
Other
PHP engine version
PHP 7.4
Web server
Apache (supported)
Database engine version
MySQL
Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 22.2.3 to 22.2.4)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
I'll be happy to provide more info if necessary.
The text was updated successfully, but these errors were encountered: