RomanZ

@mkrazz The issue is in the product core, so it affects all platforms. The good news about it is that it has very strict scenario: files get deleted only if you once deleted them somewhere AND you moved them again to same location without changing their modification time. Can't share ETA at the moment, although if related to iOS devices - usually it takes some time to get the build approved by Apple. Thanks I'll share your feedback to the team

@pascal.desmet@telenet.be Sometimes Android itself kills Sync without any warning. Are your running Sync with notificaiton icon or you turned it off? Having an icon in notification area allows Sync to run in a different mode, with lesser chances to get killed by OS.

@seltzdesign I wonder if you are using "Selective sync" folders? You can check it by right-clicking (or by folder icon - selective Sync folders show "empty" icon, while "Sync all" folder icons are solid). If this is your case, then Sync is not actually deleting files. It only deletes placeholders of actual files.

@seltzdesign That's likely due to Finder extension.Try opening system preferences, extensions, fine Sync's finder extension and disable it.

@gl00mer Could you please submit logs for me? Just send a feedback from both machines, note your e-mail and my name. Thanks!

@ddh43 Do you have any apps working with / modyfying clipboard? I suggest checking link integrity. Typical link looks like this: https://link.getsync.com/#f=Sync5&sz=0&t=1&s=HHB547MA34MBAL2QWFFLML26IA4UBUFI&i=CHSYSH7PELIRGAUEVPZFRP5FLP3CHCOOA&e=1443198421&v=2.2 I've got reports before that link had corrupt text instead of https due to 3rd party clipboard management app.

@dynosophical Yes, you can do it. Your client computer should get "read-only" key. In this case, Folder 1/2 will be delivered and kept in sync with no issues, while Sync won't touch any extra folders (as this is RO folder). Though note, that no changes from your client are going to be synced to your "source" computer.

@sbhouchen Thanks for debug logs. We'll investigate what happens.

@eldrin We'll discuss it in team - thanks for feedback. @sbhouchen It does not depend on your license. I'll appreciate your debug log, send it via help.getsync.com, mention that it goes to Roman. @garylovesbeer qoriq is no longer supported, sorry.

@cpellerano Also, JS console logs may shed some light on what happens in your case.

@xombiemp I've got your crash report, thanks. Interesting use case - thank you for sharing. BTW, does it only happens with .torrent files? Could you please try to share any other file?

@cpellerano Could you please share more details about your environment? OS? Browser? Also, did you try to run it in a different browser?

@mkrazz Got this issue identified and fixed. Please expect fix in next update.

@xombiemp While Sync obviously should not crash when opening a file, I wonder what is your use case and why do you want to open torrent files in Sync? Also, could you please send us a crash report for your Sync? It is stored in Privacy -> Diagnostic and usage -> Diagnostic and usage data -> (find the file with bittorrent sync in name). Send it via submit ticket form, note in subj that it goes for me. Thanks!

@RinaldiMe We've found the root cause - fix is coming. As a workaround, you can "touch" the file to update its mtime - then Android will no longer delete it. Thank you for reporting!

@eldrin It's not changing because of default folder mode. Its just tied to Synced mode. If you make your mode of device linking "Synced" - it will show up again. Although, I would agree that it would be useful to see devices status / ip / version regardless mode @all NAS builds for 2.1.1 are now available on our Help Center. Although, not yet on vendor app stores.

@lupus, @Hopkins While we investigate issue with MS Access in our lab, you may try the following workaround: - Close Sync - Open "FileDelayConfig" file (resides in %appdata%\BitTorrent Sync) - add the following text to the end, before trailing "}": , "​*.accdb": 10, "*​.laccdb": 10, "​*.mdb": 10, "*​.ldb":10Pay attention to the leading comma and the fact that no commas should be before closing curly bracket. - Launch Sync. See if issue still happens.

@eldrin Will you share a screenshot please? You can attach it to ticket as well @Borph Yes, its planned - though will take some time.

@kramttocs I believe this post responds your concerns.

@lux Your 2.0 (advanced) folders will work fine in 2.2. Main feature of 2.0 folders (access control) was not available for Sync Free in 2.0, so no major changes here. Auto-sync is still free. Selective Sync was part of PRO (and is part of Pro). There was just confusion about naming it: Selective Sync was called "Sync All Off". Sorry about that - we've changed name to avoid even further confusion.

@novacatz Yep. 2.2 is compatible to 2.1 and 2.0. Should be working fine.

@chadw You can just omit the --log switch. If not specified, sync.log is created in storage folder.

@zycho42, @Moe, I double checked that APIv2 is working fine in Sync 2.2.0. I was able to reproduce the issue once, when I miscopied the token - in this case I've got successfull call for GET method, and it failed for PATCH. I would advise to track carefully HTTP packets content and responses using some tool (either use wireshark, or web browser plugins).

@kamborio No need to re-add and reindex the folder. It looks like you've got a rather plain-structure folder, i.e. 190K files in a same subfolder and Sync gets a way too big chuck of service data. Try increasing the parameter "Settings -> Preferences -> Advanced -> More options -> Max torrent metadata size" to 64Mb, should be enough in your case. Let me know if it helps.

@noiime To ensure that folder_defaults.dht does not appear again, edit "btsync.postinst" file and remove the line "folder_defaults.use_dht" : ${FOLDER_DEFAULTS_USE_DHT},you can also call dpkg-reconfigure btsync once so script will clean up the default config automatically. So, to make 2.2.0 run as part of @tuxpoldo's btsync package, do: 1. Stop the service 2. Edit /var/lib/dpkg/info/btsync.postinst, remove line containing "folder_defaults.use_dht" 3. Edit /etc/init.d/btsync, remove --log sync.log (or replace sync.log with full path) 4. Run "dpkg-reconfigure btsync" so the script will update default config 5. Start service again It worked in my lab.