RomanZ

@Windlasher There are 2 options you can do to get folder in location you need: 1) Make sure your "My Devices" on peer B receives new folders in "Disconnected" state. Add folder on peer A. Observe it appears on peer B. Click "Connect" on folder line (it will be available as all folders on B now appear as "Disconnected"), it will prompt you for the folder you want to save incoming folder to. Fix the path manually if needed. 2) Move the folder with your file manager - Sync will track it if folder stays on same logical drive.

@colinabroad Just published. @kevork There is no user manual - KnowledgeBase is intended to replace it. We are monitoring on what people ask and keep it populating. For the RO folders - when devices are united in "My Devices" mesh - they cannot be read-only. We are aware of this issue and will make it possible soon. You can workaround it by kicking some of peers out of out "My devices" list.

Dear community, Sync 2.0.85 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 - UnknownError110 - which is actually a folder database corruption [related thread and workaround] - Linux & NAS are not syncing - only related to glibc2.3 version of Sync and will be fixed in next build Updated! We've rebuilt "glibc2.3 version" to fix "Linux & NAS not syncing". No changes in the code done, just updated libs.

@FredNurke There is an article on downgrading Sync. Apple does not provide a simple way to its users to use older versions of the app. If you want to share what exactly is working wrong in Sync and is willing to debug it - let me know.

@all, If there are some technical issues that you'd like to share and get addressed - I'm here to listen. The more details you provide, the more chances we can find an issue or I can assist you. If this is another topic about general 2.0 functionality or 10 folders limitation - we already have this and this - please feel free to join ongoing discussion.

@JimmyTheSaint The DB should not be corrupt when phone sleeps. We've encountered in the past couple of phone models which simply killed Sync without any warning (not giving it even a chance to save data). I wonder if you can collect and send a logcat log for your phone? If yes - I'll instruct you. You can use 1.4 folders with your phone, though it is not going to help against Error 110 - looks like your phone does something really wrong to Sync and DB is still going to corrupt. For the Linux issue - it is only related to Sync for glibc2.3, so if you got newer glibc version - you should be unaffected. Also, do you have uTorrent client on your Android? I wonder if it works well in background?

@jdrch Thanks for info. Could you please send me logs from your android?

@all The issue is identified and fixed. It is bound to glibc2.3 version of Sync only. Please expect updated build with the fix soon. As a workaround, you can use 1.4 folders - they should work fine.

@alanfluff Thanks for thorough description. If anyone has live reproduction - could you enable debug logs, repro issue and send logs to me?

@sparklellama, @alanfluff, Guys, I tried repro in my lab with little success. I've dropped you a links where you can upload data. Could you please drop there a set of screenshots or a short video on what you do and how it looks like? Thanks!

@jdrch 1) 5) 7) Mail me logs 2) 3) Known issue, there is a workaround - try adding folder via QR code (even if you see it in Android UI) - it will give you an option to choose path if Simple Mode is off. 4) Should be fixed in latest build available - which one do you use? @wimbit Same here. Contact use via support form - and we'll do our best to help you and solve your issues.

@sciurius Yes, this is the edge point. Massive files movement with tools like rsync cause a nasty issue in Sync 1.4. @colinabroad If you are willing to debug the issue - I'm happy to see logs. @kreischweide We'll do our best to speed up with bugfixes and improvements.

@JimmyTheSaint The foldererror110 indicates inability to work with DB representing the folder. Re-adding folder could be a quick solution. Also, I'll be happy to get some logs to see what exactly happened to DB. For the Linux NAS - it is most likely is known issue which we are working to address ASAP. Although, again - I can see the logs to identify it this is the issue we faced or not. Simple way to workaround it is to use classic 1.4 folders.

@kevork See this article 1.4 folders will stay as is. Not upgraded, not changed. If you create separate identity for all your Sync instanes - it will behave as 1.4 It's not about the profit stream, but more about how mobile updates are organized. We have to push updates from technical point of view as iOS users can't upgrade their devices in other way (while for many Android users installing custom APK is way too complex). help.getsync.com. Let me know if some information you are looking for is missing. @mobilediesel Yes, only one new added - config_save_interval. See whole list here. @Newuser PM me the e-mail you used - I'll resend you your code. @jeby Pretty much like any other binary. Just make sure it has enough permissions to write storage folder and sync folders. @Actron Please contact me over "Contact support form" and I'll do my best to resolve your issue.

@el_milagro There is no way to add Encrypted folder via UI in 2.0 explicitly. You have either force Sync to generate a regular key for you by adding a classic folder (hold shift, then click the "Add folder") - then you can replace "A" with "D". OR - generate it on your own. I can slightly improve your instruction on generating own keys - you need to generate 20 bytes of random data, Base32 encode them (yeah, the strange encoding containing A..Z and 2..7 is Base32) and prepend with "D" to get the secret.

@yeahhh 1. Sync 2.0 does not support background Sync yet. 2. It is by design. Just in case you delete pics on your phone accidentally, they still stay in backup.

@zbigb69 Got you! Do you remember if anything special happened before you encountered the issue? Crashes, necessity to kill app as it hang, etc?

@ManChicken Okay, so it's not the issue of slow processing of UDP packets. I suggest collecting speed profile on both your peers - we'll try to identify the bottleneck.

@ctp Sync detects file movements since version 1.2. This mechanism was improved in 1.4 and even more - in 2.0. So, Sync should track pretty well your file movements in 2.0 and not to re-download them. There are some edge cases when Sync can miss file movements, though they are rare. If you experience such issue and it is stably reproduced - I can assist in debugging it. There are some challenges when you are doing it from pure user-space applications.

@twynne Unfortunately, Sync does not support AppleScript. The only thing I can propose at the moment is controlling Sync via API. Although, it allows to operate only classic 1.4 folders.

Lars, No, somehting is wrong with your browser / downloader - just tried downloading, tarballs are just fine.

@jdrch Thanks. @all If anyone encounters - report here. I'm especially interested to know when it happened (what can bring the error) and get your logs if possible.

Yep. Looks like Versions store older copies somewhere else, not inside the file itself. Also, Apple states the similar information: When you share a document–for example through email, iChat, or AirDrop–only the current version is sent; all other versions remain on your Mac.

@ManChicken Let's try to do the following: 1. Shut down Sync 2. Open your storage folder (%appdata%\BitTorrent Sync for Windows, .sync subfolder for Linux), thre will be a bunch of Sync files (DBs, configs, etc). 3. Create debug.txt file 4. Put next data to it: 00000000<return> 0000000A 5. Start Sync 6. Do the same on second peer. This will force Sync to use TCP connection instead of UDP. Let me know if it helps.

@proactiveservices, @GreatMarko Yes, I've collected all questions / issues from this topic on EULA. Will get back here when have some answers.