Helen

@all, home folder contains your Sync user identity and license folders that are actually syncing with all your other devices and thus this message. The team is now considering a way out. So far as a workaround move 'storage_path' away from home folder, as petemir suggests.

andrewb, unfortunately, not yet.

trumpimar, We got your logs. Sorry it hard reply to everyone immediately. let's continue this in Zendesk.

@joaofl, how do you launch Sync? with a config? Check 'storage_path' or .sync folder near binary for webui.zip and check its integrity. try moving it out and restarting sync, new one shall be created. What browser you use? Any chance to try another one? @STUBR.BS, 1) make sure you do not have any crashes on this device, 2) also make sure that you have enough free space on it 3) I'd suggest reinstalling Sync with deleting its settings from local storage (for each platform it's different). Since it's really looks like something is wrong with reading from and writing to database.

@all, This is already in work with developers. For windows, what do you get in "powercfg -requests" output in Admin's Command Prompt?

Go to "My devices" -> This device -> Unlink. Key for linking devices start with "M" letter. And there are no keys for syncing files in 2.0, apart from classic 1.4 folder, key starting from A or B. How can RPi sync files using the same key as you are trying to link devices? Perhaps this article will help you to link devices?

herbert, Yes, this is on purpose. New 2.0 folders have ability to manage and change permissions for connected peers (RW, RO or owner). It doesn't make sense for bakcup folder , so they remain classic 1.4 folders.

All released builds for NAS can be downloaded from it here

teh_g, We see your ticket in Zendesk. Please proceed there.

@all, Please collect and send logs to Support Team from *both* peers involved, It'll be cool if you will indicate on which peer the file suddenly appeared in Archive and what exactly file(s) it was (were). @ninjasmurf, it's not exactly the same, though it's similar - on remote peer Sync thinks that the file is newer (for example, it was touched while Sync was off). Also, send the logs.

The app reads the folder - gets the folder tree from the system. We'll try to make this improvement. btw, new Android 2.0.80, where existing folder can be added, is already in Google Play

It's not a lie. Sync checks - "hey, are there any peers that are not synced with with folder? No? Ok, then I'm synced" - viola - 1 second ago. And it's not lazy programming. Claiming this is at least unfair. Colin, we understand all your reports, and we take into account each feedback and believe me, the team is working hard.

Colin, You know that each reported problem needs logs to determine and tell you why exactly the problem is happening on your device, in your specific environment and that specific time period. Without logs it's hard to determine. Those "date synced" BUGS are not BUGS. It's designed so. Indexing may take long time if the files are not available right now. If you could send the logs while Sync was indexing, I would tall you the pace at which it's indexing the files.

You can if you link your devices in "Disconnected" mode. Otherwise the folder will be created in default location. Also, pay attention to the following: 1) if sync was going through several updates (1.4 -> 2.0.x-> 2.0x, etc) I would suggest deleting old installation (including its config folder) and installing Sync from scratch 2) delete older .sync folder (with ID, Archive, etc) from shared folder 3) make sure you rung 2.0.93

jdrch As Roman stated above, adding the pre-existing folder on Android is a known bug and yes, the fix is coming. SyncMan, Intel processes have never and are still not officially supported. in Sync 1.4 some inner libraries (I will not go into details) were managed in a different way, which was recognized by amd emulator on Intels and let Sync run. In Sync 2.0 work with libs was changes, and no longer recognized.

right click on it -> Properties -> Details, see "Product Version" line, or just hover mouse over one of them

That's right. Deleting files "will not affect copies on other devices" . it looks like deletion was propagated from another peer, after you "reinstalled it & configured the shared folders again" - I suppose you licked it back to Server which didn't have files from Client 1. If so you will find the file in Archive on client 1

@all, This is a known issue and the team is working on a fix

Dear community, Sync 2.0.93 is available on official download site or via direct link. This build is not yet available via auto-update. Change log is available on our KnowledgeBase (from now on it will be published there). Known issues - Web UI not working on FreeBDS.

andrewanws. The most common reason for conflicts is the different letter case of files' and folders' name on peers. See details here Also, conflicts amy appear if you have symlinks in the shared folder.

angel-in, When exactly did it happen - what were you doing in Sync right before you saw the files got deleted? Were you removing the folder from Sync? Or were you disabling 'Sync all'? If yes, did you put tick to "delete files' option?

Do they still have it? how exactly did you install it? What instruction did you use? It's old Sync. Is it possible for you to run a binary on your NAS?

@all, Each "Not syncing" problem needs investigation with details on how your devices are linked, what are these devices are actually, what networks they are in, and of course, debug logging from at least two (uploading and downloading) peers. The difference between folder size on two peers may come, for example, from "Sync all" feature - if it's disabled on target machine, no files will be synced there until you do it manually.

Files may be deleted if you disabled 'sync all' option and picked "delete synced files. Or if you picked "delete files" while removing the folder from Sync. trumpimar, did you disable 'Sync all" feature on your desktop? Were the same files present in the folder on NAS before you connected them? was Sync all enabled or disabled on it? smashingtool, any details on what are your peers, how you linked them, what exactly was done in Sync and folder right before you saw it happen?

Chris, If you have linked your W7 and RPi to W7main, the former two should have the folders you add to Sync on W7main listed in Sync UI. If you have linked these two in "Disconnected" mode, then you will be able to pick location for the folder when clicking "connect". Why use "manual connection" when you have linked you machines as "my devices"? As for not being able to get past "Folder not empty. Add anyway", we are aware of it, and people who report is suddenly have it sorted out after restarting sync, or re-trying to connect folders. If it still happens, can you please send debug logs from this machine, and describe the *exact* steps that led to the problem?