Wrong character case of folder name when calling listFolder using Sync API

Ok, so this is actually now causing me some troubles on iOS. It wasn't a problem on OS X because OS X's file system is case insensitive. But it seems that iOS 8's file system is case sensitive.

So I'm copying a file from Dropbox into another folder when Dropbox notifies me that there's a new file. I create the incoming folder hierarchy and store the file.

But this is what I'm getting from listFolder now:

/attachments/5a21eee5-32b1-48e4-9a44-578234fb3285/lib_blank3:69FE45C7-3CCF-4F22-AD8E-842A034D69B5/Viveza%202%20invoice.pdf

The problem is attachments and 5a21eee5-32b1-48e4-9a44-578234fb3285 are in lowercase. There are identical folders in the file system with the same names, but with different case. For example, there's Attachments AND attachments now.

What should have happened is the 5a21eee5-32b1-48e4-9a44-578234fb3285 folder should have been put INTO the Attachments folder. And if there was already a 5A21EEE5-32b1-48E4-9A44-578234FB3285, any subfolders or files should be put inside that folder. But that can't happen now.

In OS X these folders and files are in the correct case hierarchy because the folders were created on OS X. In my current test in iOS, the folders were not created on iOS, but are being synced from the folders created on the Mac.

In fact, I have a couple of duplicated folders now that differ only by case: Attachments, attachments and Imports, imports.

Couldn't Dropbox just maintain the existing case of the files properly when returning their paths in the listFolder method?