Client: 2.6.0-daily20190522 (build 11801)
Server: 10.2.0
OS: Mojave 10.14.5
Steps to recreate:
Expected result: Not really sure. Maybe the client should offer a selection which files inside that folder should be synced?
Actual result: The folder is not synced. Basically identical behaviour as 'Synchronize none' button. If the behaviour is really the same, then there is no need for 'Apply manual changes' button
Indeed, if you make no changes to the selective sync list "Apply manual changes" will be the same as "Synchronize none". Possibly we could disable "Apply manual changes" until the user has actually made a change.
@ckamm What should I do to see the difference between these two buttons?
@HanaGemela When the "new large folder" ui state is activated you should be seeing some sync folder's subfolders pop up. Each has a checkbox for its current selective sync state. The new large folders are unchecked by default. You could have two new large folders, check only one and use "Apply manual changes" to confirm your manual choice (instead of syncing both or neither).
The same when syncing External storages
@HanaGemela Please test
Behavior change is that now the "Apply manual changes" button only becomes enabled when a change was made.
@ckamm Does it mean I'll see the button when there are two large folder to be synced?
Are the below steps to recreate correct?
@HanaGemela When you do these steps the button will be shown (as before), but it will be disabled (new). It will become enabled when you change the checked status of at least one subfolder checkbox.
@ckamm I've checked with macOS 2.6.0-daily20190616 (build 11930), I run exactly the steps described above and the button is enabled.
And what subfolder do you mean?
@HanaGemela This is what I see when there's a new "big" folder:

And "Apply manual changes" becomes enabled when I change the state of any of the checkboxes in front of the folders.
@ckamm my button is not disabled

@ckamm this still does not work
Weird. Since it's an unimportant change I'm moving further investigation to 2.6.1.
@HanaGemela I've tried to reproduce this again but am still unsuccessful.
Scenario 1:
Scenario 2:
Works as expected in 2.6.0rc1 (build 12411), mac 10.14.6