Verify behaviour with APFS

[guruz]

I know we have some issues on desktop (owncloud/client#5650) so you should check your iOS behaviour too :)

https://developer.apple.com/library/content/documentation/FileManagement/Conceptual/APFS_Guide/FAQ/FAQ.html#//apple_ref/doc/uid/TP40016999-CH6-DontLinkElementID_3
"Some differences between how APFS and HFS+ handle filenames include the following:"

Although it might be too late because 10.3 is already out?
Especially interesting might be things like emojis or invalid utf8 encodings.

[jesmrec]

Thank you @guruz, 10.3 was released time ago, ftm problems were not reported. But you are right, we had it already in mind (#857), and we should go a step further to complete a whole APFS support.

[guruz]

https://mjtsai.com/blog/2017/06/27/apfs-native-normalization/
"iOS 10.3 through 10.3.2 use the problematic version of APFS that is case-sensitive, normalization-preserving, and normalization-sensitive. You can write a lot of app code to make everything work, but anyone who hasn’t done this already probably won’t." =)