5

So I recently learned here that HFS+ is case-insensitive but the APFS on iOS is case-sensitive. Is there a publically accessible documentation/reference which describes how APFS does handle upper/lower case file names on macOS? Or has somebody tried on Sierra already and can provide examples?

  • APFS is still 'new' and will be used by iOS for sometime, no one can tell wether apple will change it – enzo Jun 6 '17 at 8:51
  • I'm voting to close this question as off-topic because it is about software not publicly available yet (see apple.meta.stackexchange.com/questions/2851/… for details) – nohillside Jun 6 '17 at 9:00
  • @patrix APFS has been in Sierra, just because this mentions High Sierra doesn't mean it's under NDA? – grg Jun 6 '17 at 9:05
  • So I modified the question to include explicitly Sierra – N. Cornet Jun 6 '17 at 9:47
  • 2
    @grgarside We don't know how APFS will handle case in High Sierra, at least not until end of June or whenever the public beta will be available. I've changed the wording of the question. – nohillside Jun 6 '17 at 10:20
5

APFS has case-sensitive and case-insensitive variants. The case-insensitive variant of APFS is normalization-preserving, but not normalization-sensitive. The case-sensitive variant of APFS is both normalization-preserving and normalization-sensitive. Filenames in APFS are encoded in UTF-8 and aren’t normalized.

The first developer preview of APFS, made available in macOS Sierra in June 2016, offered only the case-sensitive variant. In macOS 10.12.4, the APFS developer preview was updated to also include a case-insensitive variant. In iOS 10.3, the case-sensitive variant of APFS is used.

Apple’s Developer FAQs

  • Does it mean that the user can choose the variant if both are "included"? – N. Cornet Jun 6 '17 at 11:19
  • I just did the upgrade on my dev machine and It purely had a checkbox to upgrade with no option to select the type. The volume is now not case-sensitive. – Nick Potts Jun 6 '17 at 11:24
  • 3
    Without a definition of normalization-preserving and normalizatino-sensitive this is rather difficult to understand. Also, the comment about "upgrading a dev machine" gets us back into NDA territory. – nohillside Jun 6 '17 at 11:29
  • 1
    For an example of some normalization concerns, see eclecticlight.co/2017/04/06/… – Tom Gewecke Jun 6 '17 at 11:56
1

Since many apps have not been updated to work with case sensitive file systems, Apple probably decided to do the upgrade with case insensitive by default. Hopefully as apps get updated the default in a future MacOS will change to be case sensitive.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .