GreatMarko

Looks promising!

The purpose of the logs is primarily to allow support/devs to troubleshoot issues when they arise - as such, they're not designed to be overly "pretty" or contain detailed "human friendly" explanations as to the meaning of each entry for the benefit of end-users - they're designed to be as concise as possible and contain relevant information for the benefit of technicians to allow them to diagnose problems.

@rockhill, sorry to see you go - especially as it's been confirmed that the fix for this exact issue is to be included in the very next update to Sync!

Why would this be needed? You can already set links to require "approval"!! For example: Step 1) I generate a link for you Step 2) You click the link Step 3) I receive a notification in my Sync that you've clicked the link and can then confirm/reject whether you're allowed to start sharing with me ....give that, what would be the point in having "password protection" as well!!??

Please see: What is a key and how does it work?

From the Unofficial FAQ: "Note: If you currently use the auto-update feature of BitTorrent Sync, it may inform you that your "Client version is up to date" despite a newer build being available. This is intentional whilst Sync remains in "beta" - new builds are currently announced here in the forums in the first instance. Not every "beta" build is pushed via auto-update, only those considered significant/more stable. Even then these may not be pushed out to existing users via auto update until several days/weeks after they are first announced on the forums"

What type of files are you having problems saving? - They're not Office files by any chance are they? - if so, please see this thread.

Check your config file - by default, Sync 1.4 only listens on the loopback interface (localhost/127.0.0.1), so you will need to change the webui "listen" parameter in your config file if you wish Sync to listen on a different IP (or set it to 0.0.0.0:8888 to listen for connections from all IPs)

I believe the default state is for auto-sync to be off - and so it's likely that you inadvertently turned it on at some point, which then caused your iOS device to try to download the entire contents of the folder you were syncing. Anyway, I'll now close this thread, as the functionality you desire does exists in the iOS app, and therefore isn't a "feature request"

Simply turn the per-folder "Auto-Sync" setting off, and that's then exactly how the iOS app works!! Please see: Selective Sync and Auto Sync

@jadubyasee, try turning off "Simple Mode" (Settings -> Advanced) on your Android device

I think most people realize that "OSes with IE older that IE9" includes WindowsXP/Server 2003, etc (which can only run versions of IE older than IE9) - however, we're going in circles here - the fact is: As of Sync 1.4.82, Windows XP is supported

@Dva, good news! - there is now an official alternate download location for the latest Android .apk (1.4.56): http://syncapp.bittorrent.com/1.4.99/android-google-release-1.4.56.apk

@mike20021969, my earlier post that you refer to in the now obsolete "Latest Desktop Build 1.4.75" thread was from 3rd September, and was correct at time of writing. However, since then, and following feedback from users, the developers re-introduced support for XP (and other IE8 based systems inc Win2K3, etc), which arrived in 1.4.82.

Files you add to a read-only node will be ignored, and won't propagate to other devices. You can use the "Overwrite any changed files" option in that folder's preferences to bring the read-only node back in-sync with any full-access nodes it's connected to

@Malslo, those particular icons apply to Sync 1.3, and are no longer applicable to Sync 1.4 - I'll update the FAQ accordingly now. In 1.4, connections are direct, unless otherwise indicated by a icon next to each device when you open a folder's Peer window

1.4.99 has since been released - please try that and see if it resolves your issue. (Incidentally, the randomized ports issue which RomanZ suspected was linked to your issue was resolved for 1.4.93)

Step 1) Note down the folder's current key (secret) Step 2) Remove the folder from Sync Step 3) Move the folder to its new location Step 4) Re-add the folder in its new location back to Sync using the original key from Step 1 Step 5) Sync will reindex the folder, but nothing should transfer/sync with your other clients

Did your receive a test build on the 30th October or 31st October? The reason I ask is that the test build available on 30th October (when RomanZ first posted in this thread about a test build being available) didn't resolve the issue. However, a further updated test build was made available a day later on 31st which does appear to resolve this issue.

The latest build thread actually refers to this thread for information/reference - not for a workaround/solution.

@joncamfield, please update to 1.4.99 as this contained a fix for non-ASCII character issues

Yes - .SyncIgnore doesn't apply to 1.4 In 1.4, .SyncIgnore has become .sync/IgnoreList (i.e. you'll need to edit /opt/customer_home/.sync/IgnoreList)

This is a known issue with 1.4.93 - it is fixed for 1.4.99. Please be patient, 1.4.99 was only released yesterday - Tuxpoldo hasn't had chance to update his packages to this latest build yet - which he does in his spare time.

The issues with Encrypted nodes should have been addressed by this update - can you check that you've update all your nodes to 1.4.99?

Sorry, at present the Android app is only officially available through the Google Play Store.