luomat

We've ben waiting for a new official release for months.

Are you running macOS Catalina? Try adding it to "Full Disk Access" in System Preferences >> Security & Privacy

At this point I am expecting a new 3.0 version which adds a ton of features in addition to addressing any outstanding bugs. What else could explain the delay?

So you sync them, but they don't sync. Unless they're in a folder. I'm glad you clarified that. I stand by my original comment 🙂

You would have to put that file inside a folder. Resilio Sync does not sync single files, only folders with files within them.

Looking at the change log and the forum posts for the last three releases: 2.6.4.1344 - December 27, 2019 - contains literally one fix 2.6.3.1340 - January 14, 2019 - 4 lines in the changelog 2.6.2.1330 - November 22, 2018 - 10 lines, a reasonable release So we had two releases in all of 2019, and one of them was literally just a single issue security fix. We went through all of 2019 without a significant release. It's not unreasonable to hope for something more if you want us to believe the app has not been abandoned. As for Frank's complaints about apps that update "too often", well that hardly seems relevant. Maybe there's a huge 3.0 waiting in the wings… but if that's the case, I hope a beta will be coming out soon.

Assume that by "soon" I mean "within the next 4-6 weeks".

Sorry if this is obvious, but in case you haven't tried it… try turning the setting off, make sure it's NOT in "Users & Groups" » "Login Items" and then try turning it back on.

Are we likely to get a new desktop build anytime soon? It's been ages.

I don't think you can use Sync to sync two folders on the same computer, even if they are not on the same drive. Last time I tried, it just refused to add it.

Sounds great. I really like the app and don’t think there’s anything quite like it available, so I am hopeful that it has a bright feature.

Thanks @Alex. I hope 2020 will see Sync back on track. I appreciate all of the help you’ve given on the forum during the past year which seems like it has been a difficult season behind the scenes.

I have been using version 2.6.10061 which was previously released (only on the forum, as far as I know) to fix other issues. Does 2.6.4.1343 include the fixes from 2.6.10061? If not: Why not? 2.6.10061 has been around for a long time and we’ve seen no new builds. What do I do if I need the fixes contained in 2.6.10061 ?

Well, if you know the results, then the wording should be fixed. If you think that they’d come up with Sync’s definition, you’d be fooling yourself.

Go out and ask 100 people what “pause” means in the context of an app that syncs files, and let me know how many of them come back with your definition.

If I wanted to stop all activities, I would quit Sync. But if I want to stop activity in just one folder then PAUSE ought to do that, not some other definition of PAUSE that NO ONE WOULD EVER ASSUME because to everyone else in the world PAUSE means PAUSE not PAUSE SOME THINGS BUT NOT OTHERS. This is either a bug or a terrible idea by some engineer. As the feature now exists, it should not be called PAUSE under any reasonable definition of the word PAUSE which a normal person would take to mean “Nothing will happen to this folder until I tell it to resume." The ability to pause some folders (and leave others syncing) is one reason that I chose Sync instead of Dropbox. If I wanted to have to quit the app to stop all syncing, I can just use Dropbox.

This really is a terrible design flaw. If syncing is paused, I expect that to mean that changes I make locally have no effect remotely until I resume syncing again.

I sent a feature request on Nov 22 and had it acknowledged by Alex Witz on Nov 25, but I haven’t had any actual support requests for awhile.

I just noticed that ~/Downloads/.sync/ has a lot of “!sync’ files: total 454068 0 drwxr-xr-x 59 tjluoma staff 1888 Dec 10 18:47 Archive/ 9600 -rw-r--r-- 1 tjluoma staff 9440950 Oct 24 08:29 '006393D28530D7D9A5B19805E903876B4AA748C7.!sync' 6176 -rw-r--r-- 1 tjluoma staff 5489126 Nov 2 01:02 '0CE0E3307A486A196AD2619525F2424B6B3145C0.!sync' 87168 -rw-r--r-- 1 tjluoma staff 72513878 Nov 2 01:02 '10A0C70965D9DB9383899141C754A93D666EFEA1.!sync' 89760 -rw-r--r-- 1 tjluoma staff 83416967 Nov 2 01:02 '162BD2AF7A263DDADB1255C1EF491EAE20031F4E.!sync' 6176 -rw-r--r-- 1 tjluoma staff 5999978 Nov 2 01:02 '1D7FD581C408D57489921F37676AB2E8A6D7026A.!sync' 9536 -rw-r--r-- 1 tjluoma staff 8775733 Nov 17 20:45 '3E8A676D48CDFB728ACB21B1BFE82E72D4D7B3FD.!sync' 15776 -rw-r--r-- 1 tjluoma staff 15718146 Nov 2 01:02 '42BB70899EC91CC0BCDF36D7C6371B04210793D6.!sync' 4 -rw-r--r-- 1 tjluoma staff 793 Nov 2 01:02 '47A3DEB2CE7CF336B0395A341BDBFD1766D0FE78.!sync' 22016 -rw-r--r-- 1 tjluoma staff 21519426 Jun 30 12:51 '4A4E6C79DC227DFDA78D0D23B336432C9574568D.!sync' 4 -rw-r--r-- 1 tjluoma staff 1338 Nov 2 01:02 '5620DF4C74B2639B0D2E38EB88C9411429B3A1A1.!sync' 4 -rw-r--r-- 1 tjluoma staff 335 Nov 2 01:02 '5A245B2F04737EE969EC7B385009942D129DF3DD.!sync' 15264 -rw-r--r-- 1 tjluoma staff 15598739 Nov 2 01:02 '6A040F9091E7E34884DA2C5587D664D07FF0BB6B.!sync' 4 -rw-r--r-- 1 tjluoma staff 1384 Oct 24 08:29 '753191B0BA822ED0B2AB50B53BE10FB6E0C813FF.!sync' 4 -rw-r--r-- 1 tjluoma staff 521 Nov 2 01:02 '7A33F0CE4835B1D56FB5DFA8809410C020DDBF3B.!sync' 992 -rw-r--r-- 1 tjluoma staff 975500 Jul 10 00:33 '7EB669356D198FC51E4F9EBE3FCBAD0FA73FDD07.!sync' 4 -rw-r--r-- 1 tjluoma staff 57 Oct 24 08:29 '82A61654D5A598C6663FFAE04B9149FEA54CA617.!sync' 4 -rw-r--r-- 1 tjluoma staff 288 Nov 2 01:02 '880357B8117AE0A106ACBC7CCD9B3D8F7C31F08E.!sync' 7584 -rw-r--r-- 1 tjluoma staff 7279443 Nov 2 01:02 'B2D338EE9E8CA2EBDCED10D5948E4FBA0C8D834A.!sync' 57600 -rw-r--r-- 1 tjluoma staff 58965914 Nov 2 01:02 'BB754FDD71B9872BA60AF3291E2DE573C9D79243.!sync' 4 -rw-r--r-- 1 tjluoma staff 1160 Nov 2 01:02 'BE10B54D3793BA3ED5D4B3727976DDE4980148F4.!sync' 14400 -rw-r--r-- 1 tjluoma staff 14183977 Nov 2 01:02 'C0524E5A2867177864DBBDBC0A3AD14199A911EA.!sync' 49888 -rw-r--r-- 1 tjluoma staff 50410272 Nov 2 01:02 'CCCD8FA699653287224A72089C617D5E2BEED54F.!sync' 320 -rw-r--r-- 1 tjluoma staff 327680 Sep 19 23:24 'D4C527D796E3B7D0B5BD4DA15DF0C0E92B39CDD0.!sync' 5792 -rw-r--r-- 1 tjluoma staff 5406528 Nov 2 01:02 'D5A5C37E8610F1B1D79A1B0C47716AF29CA11B12.!sync' 4 -rw-r--r-- 1 tjluoma staff 1155 Nov 2 01:02 'D8B9742A1432831D0FBB9FFF8EB5285E84CBFC34.!sync' 17472 -rw-r--r-- 1 tjluoma staff 17630000 Jul 30 07:47 'D8FB556DAB157AA70B4D78F8F12805F1C19FB741.!sync' 38496 -rw-r--r-- 1 tjluoma staff 38746857 Nov 2 01:02 'DEB0B3064FBD3BB8166B856AD934454FB3B5A4EB.!sync' 4 -rw-r--r-- 1 tjluoma staff 700 Nov 2 01:02 'FDBE9E1D5D252A05DE9EBEEC718090CA9B741E4D.!sync' 4 -rw-r--r-- 1 tjluoma staff 32 Nov 23 01:29 ID 4 -rw-r--r-- 1 tjluoma staff 642 Aug 1 10:06 IgnoreList 4 -rw-r--r-- 1 tjluoma staff 275 Jun 26 10:34 StreamsList 0 -rw------- 1 tjluoma staff 0 Jun 26 10:34 root_acl_entry I assume these are files which were not successfully transferred to this local machine. Is there any way to find out why they failed to sync?

I don't think this is possible with Sync as it currently exists. If PC1 and 2 are Unix-based, you could do this with `rsync` (with any 'delete' args) but that's not really what you're looking for.

I don't understand why you wouldn't make it 2.6.4 since the 1340 isn't shown in the app build numbers (neither `CFBundleShortVersionString` nor `CFBundleVersion`)

Done. Thanks. That seems to have fixed it. 13 days to get a response to a bug report isn’t great. Is there a better place to report them than here? I’m curious to know how Resource Forks suddenly became an issue in 2.6.3. After all, it seems like an issue that Re-Sync would have had to deal with from the beginning. Version 2.6.3 has been out for awhile. Was I somehow the first person to report this issue? That seems odd. Update: I’ve just seen this post which suggests that the past few weeks aren’t (hopefully!) indicative of “normal” for the company. So that’s good news.

I have a very large folder syncing between two Macs: both Macs are running RS version 2.6.3 Both Macs ".sync/StreamsList" files include "com.apple.ResourceFork" Nevertheless, they are trying to sync a large amount of com.apple.ResourceFork files, as shown here: What should I do to fix (or even troubleshoot) this?