I received a message today that my NextCloud client needed to be updated. I updated to the latest (3.16.3) MacOS client, but when I did, it asked me to select my sycn folder, which I tried to do. Unfortunately, when I try to select it, it tells me that the folder is already a sync folder and wants me to choose a new folder (and I assume) to resync almost 1TB of data.
I have never had to resync when updating my client, so I am wondering why it is telling me to do so now, and moreover why it won’t just let me select my current nextcloud sync folder.
I have 30 laptops that I need to update to the new client (according to the message) and I really cannot afford to have to pull them all back into he office to resync 1TB of data each, so I am hoping someone has a good idea or a solution.
I would also expect that it recognizes a previous setup (config settings should always be in the same location)
Which version were you using before? Then perhaps, something important like the config settings or so have been moved?? It is worth then checking what has been changed, or if you had a very old version, and there were several changes over time…
(the newer versions are supposed to support virtual file sync, where it mainly keeps just the full folder structure and just downloads files on demand). You can ask to keep certain files offline. And sure, disable it and have the classic mode. This was first introduced to Windows, and then later to Mac and Linux.
Hello - I was using 3.15.3 before and just received a notification that I had to upgrade which I did. I did it as I normally do, I downloaded and installed the latest version, no other changes, didn’t change the install location or anything at all.
I just tried it on another laptop, exact same results. Upgrading from 3.15.3 to 3.16.3 immediately requires me to connect back to my server and then wants me to resync everything.
Is there anyway to go into the client config file (wherever that may be located) and manually point to my exciting data sync directory?
I have no current macOS, but the config files should be in this location:
If you can find different configs in your system, you see perhaps the old/new at a different location. You can probably replace the configs when the client is not running.
I didn’t spot anything on the bugtracker, but if you can identify why this happens, it might be interesting for a bug report: GitHub · Where software is built
Just if it was a general issue, I would expect it to be reported already.
Thank you! I was able to launch the logwindow and see that for whatever reason the old configuration file was not able to be moved over to the new place nextcloud wanted it. I shut down next cloud and copied it manually and restarted nextcloud and all was right with the world. Thank you for taking the time to help.