I just ran into this error ("BitTorrent Sync cannot identify the destination folder") myself, which is pretty non-descriptive/unhelpful for the user. I tried disconnecting and reconnecting the folder, but it would not connect. Specifically, the connect dialog box displayed the message "foldererror110" and clicking "ok" wouldn't do anything. I then tried removing the folder in BT Sync (but not deleting the original files) and re-adding it. It told me that the folder is owned by another Sync instance and asked if I wanted to reset ownership. I chose yes, but then the program wouldn't sync the folder - it showed 0 of 0 peers and 0% progress. I closed and reopened the program, at which point the 0% progress message went away, and it correctly showed 0 of 1 peers. My connected (Android) device, however, then showed unknown error 110. I disconnected the share on my Android device, and it loaded the new share, but automatically created a duplicate folder for it. I exited BT Sync on my Android, moved the .sync folder from the new/duplicate folder to the old one with the data, reopened the app, disconnected the share, and tried to reconnect it. In the connect dialog, I entered the existing folder (which has the data and .sync). When I tap "Add Folder," however, the share remains disconnected and there is no message/feedback from the app. I next tried exiting the app, deleting the .sync folder from the shared directory on my Android, reopening the app, and reconnecting the share using the existing directory, as above. This time, however, instead of connecting the existing share, the app created a NEW share, which then started syncing to my other devices. At this point, I'm giving up. This is beyond messed up. Why does the Android app handle folders with existing/seeded data so badly? Why doesn't BT Sync have a process to handle a corrupted folder ("cannot identify")? What's going on with all the other issues?