Apple now states that APFS will handle the problems of normalisation of file and folder names. At least in iOS 10.3.3 and macOS 10.12.6, due shortly.
Did Apple secretly alpha-test file system conversion in the iOS 10.0, 10.1, and 10.2 updates – without informing users or letting them opt-out of testing?
Free, works with Sierra and other unified logs, examines log entries already in the log, unlike Console. Now supports logarchives and more.
This version allows you to open, browse, and analyse any .logarchive bundle, from a Mac, iPhone, iPad, or more. Ideal for forensic analysis.
macOS doesn’t work like it used to. With heuristic task dispatching and sensitivity to factors like quality of network service, troubleshooting can get fiendishly difficult.
Apple spills some of its beans to a select group of the press, and we start to explore the new features expected in macOS 10.13.
Case-insensitive APFS is not at chaotic as the case-sensitive variant. But there are still plenty of problems which developers and users need to prepare for.
APFS is not currently safe to use with names which might have Unicode normalisation issues – which means it is only safe with a limited ASCII character set.
Practical demonstrations, a new free tool to explore the problem, and examples to illustrate the issues which could arise with APFS.
The switch to Apple’s new file system seems to be going very well. Except that an old problem is now becoming apparent: how to name files and folders.