Impossible to register new clients for existing database in Dropbox

[cleanbit]

I've noticed that sometimes to some users it is impossible to register (and open) existing database in Dropbox on a new device. Some TICoreDataSync operations begins and never finishes. The reason to this is that responses from Dropbox returns paths which contain folder names in lower case, while on OSX/iOS they have different cases and those paths are compared with isEqualToString:. Comparing paths while ignoring case fixes this issue. Sadly, I cannot to reproduce it yet with my own data which I cloud share, however one user sent his entire TICoreDataSync folder. It is reproducible every time on different devices with that folder.

2013-11-13 17:21:08.625 -[TICDSDocumentRegistrationOperation beginCheckWhetherRemoteIntegrityKeyMatchesLocalKey] : Fetching remote integrity key
2013-11-13 17:21:10.373 -[TICDSDocumentRegistrationOperation fetchedRemoteIntegrityKey:] : Setting local integrity key
2013-11-13 17:21:10.375 -[TICDSDocumentRegistrationOperation beginCreatingClientDirectoriesInRemoteDocumentDirectories] : Creating client's directories inside the document's   SyncChanges and SyncCommands directories
Printing description of result: // this is metadata’s content
{
    bytes = 0;
    icon = folder;
    "is_dir" = 1;
    modified = "Wed, 13 Nov 2013 15:21:20 +0000";
    path = "/com.test.sync/documents/47749eab-d1cc-45a0-8234-2bb1239809e4/SyncChanges/3B647975-6D45-4EF0-8020-182CF1B6B3C2-12936-00000F1FB489DB21";
    rev = a9f1533f10b;
    revision = 2719;
    root = "app_folder";
    size = "0 bytes";
    "thumb_exists" = 0;
}
(lldb) po path
$8 = 0x170c86d0 /com.test.sync/documents/47749eab-d1cc-45a0-8234-2bb1239809e4/SyncCommands/3B647975-6D45-4EF0-8020-182CF1B6B3C2-12936-00000F1FB489DB21
(lldb) po [self thisDocumentSyncCommandsThisClientDirectoryPath]
$9 = 0x170ae530 /com.test.sync/Documents/47749EAB-D1CC-45A0-8234-2BB1239809E4/SyncCommands/3B647975-6D45-4EF0-8020-182CF1B6B3C2-12936-00000F1FB489DB21

[kevinhoctor]

Thank you for pointing this out. I haven't seen this exact problem, but now that I'm aware of it, I'll review some of the bug reports coming in to see if this is the cause.