Helen

1) will be empty if: - it's disabled - updated files are more that 1000 Mb (max_file_size_for_versioning in Advanced settings) - files you update/delete on Mac are not actually downloaded to Win (Win is in selective mode and files are presented as placeholder.bts) 2) Sorry, could not reproduce. were older files placed right after you updated them on Windows? is Date&time correct on Mac - did you move it to the future?

Merk7, are they in sync queue on both peer? It's better to send the logs to the team for analysis . Database error is explained here the upgrade from 1.4 to 2.0 may be not smooth enough. Try completely reinstalling Sync (including its settings), so that new configs were recreated.

salzrat, Background activity is in our wish list, but it will require creating additional infrastructure, so it will take some time and is not likely to be implemented in the near future. Thank you for understanding.

There were same database corruptions in Sync 1.4, but then syncing was not stopped. This might have lead to bad results with files corruption, incorrect syncing, etc, well because database is corrupted. Now, when db gets damaged, syncing stops and error message appears. @jdrch Many Android devices are known to kill Sync in background with "Force stop", which is not a good way to let an app finish its work and save its configs and database, so corruption appears.

Archive is not fully disabled on Androids. Files stay there for 1 day. Is it possible to set phone to back up to C:\Users\User\OneDrive\public\Pictures\phone, not C:\data\DCIM? Plus, when you delete files from your phone, they are not deleted from connected devices. this is how backup works. But make sure you have the files actually *synced* to your PC, before deleting them from the phone.

Mac is still under investigation, but we cannot reproduce it for Windows. @jdrch, Thank you, but do I get it right and Sync is not on the list? Anyone who has this problem with Windows, Sync preventing it from sleep, any details? At least "powercfg -requests" output?

@narnold1, What is your device? And how exactly you change the folder, I mean, on which exactly step the app crashes? The issue Roman mentioned is fixed in 2.0.80 -when you disable "Simple mode", Sync will allow picking the folder location while connecting the folder

In those cases where the problem was caused by Sync's code, it was fixed in Sync 2.0. However, this problem also has a number of other causes depending on the workflow and environment. Such cases still require debugging

@krso92, "Sorry file doesn't exist on our system anymore." - no log. Can you please send the logs to the team per this instruction , it also tell how to send logs from mobile.

salzrat, We know about this guideline. Thank you.

No, it's not. Conflicts appear due to different letter case. If you add a 'healthy' Filename.ext to the folder, and 1) there is no such file on the other side at all, but 2) the conflict still appears, these are the possible causes: 1) there is actually a filename.ext on the other peer 2) not all conflicts were removed from the folder (before putting the healthy file back to the folder) 3) there are still conflicting symlinks. Can you please send debug logs to us. Please indicate what are your devices and what exactly files/folders are creating Conflicts.

Merk7, what is your network? what are your devices and sync version on them? what types of files you sync? what exactly history says about mistakenly synced files? There should be something like 'peer X updated/renamed/removed file'. Are these files located in symlinks (in case you use Windows) During those 3-4 hours, do you see any up/download speed indicating that syncing is in process? If it's some few Kb/s, the files re not syncing actually. Try restarting Sync or re-adding the files to the folder. Sending logs for analysis would be perfect

It's on intel processor, which it not supported by Sync. The answer to a possible question "Why 1.4 was working then?" is already here

Sorry, we cannot promise it. but we also want to have it fixed ASAP. and yes, the team do work on this.

mikebarber1, What are your machines? If it's a windows, do you have symlinks there? Is it them where conflicts are created?

Stonefred, Does he have a 'crossed pencil' icon on this folder? If not, then this is RW folder. Also, open this folder preference (in Sync) -> View key and see if there is A&B pair or only B key. If A&B pair, than this is RW folder. How exactly were you sharing the folder from your machine - via link or key (if you shared 1,4 folder)? Please see these folder types so as not to get confused.

The difference is that they all have their servers (clouds), from which they send push notifications and wake the app up. Sync doesn't use any clouds, it has nowhere to send the push notifications from.

@all, just to be sure, for those who haven't done it yet, can you please check and tell me under what user the updated Sync runs now and if this user actually has RW permissions to sync folder?

Unlikely. was Sync shut down correctly? or was it a "force stop"? This error will appear because database got corrupted. And this may happen if Sync was not closed correctly (for example crashed) and was not able to save its database

Well, they are actually keys for linking devices. Just a common 1.4 key. hmmm, am I missing something simple and obvious here? Do you open mp3 right from Sync app and have them opened in Spotify? Then soft button (it is what you mean) 'back" will close it.

Threshold, Link your devices in "Disconnected" mode. Then you will be able to pick location when connecting the folder. Details are in this topic, this topic and in the guide (here with screenshots)

TucuUK, And what about crash? If it still happens, please send full crash dump to us.

@salzrat, "Automatic backup" means that newly taken photos and videos will be automatically backed up,,,, yes, when Sync is in foreground. iOS kills apps in background (apart from a limited number of them), so Sync is just stopped.

AtariSoul, Which version of Sync you run on the phone? Update to 2.0.80 if you haven't already.

It cannot be removed, unfortunately. This is not yet fixed.