Skip to content
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

2.7.0 beta: forgets all folder synchronisation status #1750

Closed
tobiasKaminsky opened this issue Jan 22, 2020 · 4 comments
Closed

2.7.0 beta: forgets all folder synchronisation status #1750

tobiasKaminsky opened this issue Jan 22, 2020 · 4 comments

Comments

@tobiasKaminsky
Copy link
Member

  • use 2.6.x
  • have some folders not scheduled for sync
  • upgrade to 2.7.0 beta
  • see that client wants to sync everything
  • verify that all folders are scheduled for sync
@doits
Copy link
Contributor

doits commented Jan 26, 2020

Looks like it downloads everything again, too, even if files are present/unchanged. Edit: To be more precise, everything that is added back to be synchronized.

E.g.:

  • Folder A is not synchronized anymore because it is larger than 500MB and the default limit is set
  • Files are still present on disk though
  • Folder A is manually set to be synchronized
  • Everything of Folder A is downloaded again, looks like existing files are overwritten

@mr-manuel
Copy link

After upgrading from 2.6.2 to Version 2.7.0beta1-Win64 (build 20200119) I had to quit and start Nextcloud Desktop app 7 times to be able to display all synced folders (7 folders). After every restart of the Nextcloud Desktop app one more folder appeared.

In my case a resync of all files did not happen.

Additionally the right click on the tray icon doesn't work anymore.

@thejulian
Copy link

Faced this issue today on one of our employees. Updated from 2.x.x to 3.0.2.
Is there a solution to this? Or a file someone can backup on daily basis which contains sync-information?

@er-vin
Copy link
Member

er-vin commented Sep 29, 2020

Looks like an older duplicate of #2279

@thejulian I will close this one (and #2279) is closed as well because we did a fix for it. What concerns me is that said fix made it for 3.0.2 and was reported to work, I wonder if you hit something different. Might be worth making a new full fledged report with as many details as possible... I understand it's harder to upgrade time events though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants