RomanZ

@mh5bl The Android app has no "History". There are only debug logs and one can send it to our support using feedback form. Note, that usually to understand where the issue is - we'll also need debug logs from your desktop computer / NAS.

@all BitTorrent Sync is not intended to Sync data locally, only across network. So @12345lamacun is right - you'll need to run Sync instance on server to transfer data there.

@kbahrami It means that Sync is unable to to sync the file by some reason. I suggest turning on debug logs on your PC and sending me debug logs from both PC and your iOS device once issue reproduces.

@heehee62 1. Sync for iOS is not working in background, so you'll have to open the app to let it sync. 2. It is possible. Try pressing the context menu button -> New backup -> Custom location.

@swerb Try setting the "Overwrite any changed files" preference for the RO folder and see if it helps.

@max302 Sync does not operate ICMP directly, though ICMP is widely used by network entities (like gateways, routers, etc.) to error report and control what happens to IP packets in network. So, as @proactiveservices mentioned, it is not recommended to disable / block ICMP if you want your network work smoothly. See here more for details.

@jake.sadie All the requests in 2.0 forums are reviewed and filed (if they are new and non-duplicating). It just takes time to process everything and respond. For #1 and #2 your requests - you can choose arriving folders location if your "My devices" setting shows folders as "Available" by default. Then you can choose whatever location you want when hitting "Connect". Does it works for you? For the request #3 - it looks very similar to one of your initial posts asking to hide some of folders you never want to see on some of your "My devices" mesh. I.e. it could be covered with "Don't show me this folder anymore" function, correct?

@colinabroad All experimental builds are side branches (i.e. they never updated with fresh fixes) and are built on top of some release build. The 1.4.10005 is based on 1.4.103 and it does not contain any fixes from 1.4.106. As soon as 1.4.10005 proves working - we'll deliver it to maintrain (1.4.107 or above). You already participated testing and reported results, so no need for another test. We need more reports from other users suffering same issue.

@colinabroad I've moved your question to relevant topic

@Journeyman, @JoeJoomla I've sent you the experimental build. Let me know your testing results.

@JoeJoomla I've got an experimental build fixing the Out of Sync issue. Let me know if you are willing to test it.

Dear community members, We have a possible fix for the "out-of-sync" issue. If anyone suffering this nasty issue is willing to test experimental build with the fix - please contact me over PM or just leave a message in this topic. Experimental build is compiled on top of 1.4.106 (so contains all the fixes that are in .106 build as well). Installation is pretty simple (just get the binary, shut down the sync and overwrite old binary with the experimental one).

The "Download site" link is always the same. There were an unexpected delay in delivering builds to download site, I apologize for that. @colinabroad 1. Locked files issue is still there. The issue is cosmetic and is not planned to be fixed as part of 1.4, though is fixed in 2.0. 2. Microsoft office compatibility issue is not fixed yet, we are looking for volunteers to test the possible fix at the moment. In the "Known issues" section we publish issues we are asked a lot about by community members / users via support channels. The full list is huge and there is no sense to publish it here. I also see no point in publishing the priority and issues being analyzed at the moment - this is internal information and it changes rather quickly. "Minor issues" are issues that do not affect user experience. All changes that do change Sync behavior are mentioned in change log.

Hi @elex, It looks like the issue of constant re-indexing is bound to some particular file(s) which can't be synced. Could you please increase log size to 1Gb, reproduce the issue and collect the logs? I'd like to make sure if you have the same root cause or you've got something different.

@all If one specifies a peer in "Predefined host" - Sync is going to behave like it knows there is a peer for sure and attempt to connect there over unicast TCP / send UDP datagrams. The "Search LAN" works differently (and it is NOT using broadcasts) - Sync will: a ) Subscribe to multicast group 239.192.0.0 to receive notifications from other Sync instances b ) Send multicast packets to group 239.192.0.0 over port 3838 for around 10 seconds when Sync starts up or detects some network interfaces changes - to inform other Sync instances about its presence. Multicast packet contains no private info - it delivers peer ID, share IDs and the port to connect to. Also, all multicast packets have default TTL of "3", so it depends on company routers and appliances configuration on how far multicast traffic will propagate (usually, "1" means - restrict to local subnet, <32 means - restrict to same organization / site). @vw183 For your case I see 2 optimal solutions 1) Set up own tracker server in your LAN (not yet supported, although we'd like to implement it in future). 2) Enable "Search in LAN", make sure that routers between networks will drop multicast packets with TTL<4. If you've got "multicast-aware" routers, they won't generate too much traffic.

Hi Patrick, Not yet - though we are working on it. 2.0 is not yet fully compatible to 1.4, and we'll releases a new 1.4 version soon which will be fully compatible with 2.0.

@UmedaBound Could you please elaborate - which Galaxy Note? Samsung have released several editions.

Dear community, Sync 1.4.106 is now available on download site. Here is direct link. It is NOT available via auto-update yet. Change log - Fix crash when running binary next to settings.dat file - Improved debug logging - Fix issue with Sync icon not updated during switch between light / dark theme (MacOS) - Fix out-of-sync issue (PowerPC only!) - Fix issue with IgnoreList not working on Sync startup - Fix issue with Sync inability to start on MacOS when user folder is moved to another drive - Minor issues fixes Important Notes on Sync 1.4 Downgrade to 1.3 is not possible after installing Sync 1.4. (If you wish to downgrade - please uninstall Sync removing all settings, then install 1.3 and configure all folders from scratch) Important Notes for Sync 1.3 Users Windows XP and Server 2003 clients using Sync 1.3.x will not receive auto-updates to 1.4, but can still update to 1.4 manually. Known issues - UI is tiny on high resolution displays [Workaround] - Sync may continually re-index SMB shares [Discussion] - Renamed files are logged as New Name → Old Name (instead of Old Name → New Name) [Discussion] - Checkboxes once selected may move out of alignment on OSX Yosemite [Discussion] - Certain models of Android mobile devices cause deleted files to return with 0-size

@JimmyTheSaint History is stored in separate file starting from 1.4. Please see the "history.dat" file in storage folder (though, it is not text format - it is bencoded).

@sciurius We are also working to improve debugging and self-help experience in future releases. Hopefully it will be not as painful in future.

Bradley, Thanks for info - please keep me updated.

@all Anyone else suffering the subj is willing to test experimental 1.4.10005 build?

Steve, Even the best lab environment is different from real world usage. Indeed, we've released a build wit "fix failed" for this bug. Hopefully, we'll fix it soon and fix will be fully functional.

Sorry for that. I meant "Name", the typo + text autocorrection made my question a bit cryptic. I have asked about the name as it reproduces only on certain subset of devices - and never pops up on others (for example, it does not repro on Galaxy Sx in my lab). Thanks for reporting - I don't need any more data at the moment. If I'll need something else to debug the issue - I'll approach you.

@lupus We are working hard to make Sync more reliable. Hope to see you using Sync again later - when the issue is finally resolved. Sorry for inconvenience.