We request clarification of a Foundation API discrepancy from existing read-only diagnostics.
Environment: the user has personally run sw_vers on the currently running Mac and confirmed ProductName: macOS; ProductVersion: 27.0.1; BuildVersion: 26A434. This is the currently confirmed system version. The reviewed records do not establish an unambiguous temporal link between that confirmation and the APFS/Foundation measurements on 15 November 2026; we therefore do not assert that it proves the OS version used for those measurements. Earlier macOS 26.6.2 (25G83) records are historical and are not presented as the current system.
Observed volumes: External APFS Volume A and External APFS Volume B, both external APFS volumes connected over USB.
For BOTH volumes, the recorded diskutil results are:
Encryption=true; EncryptionThisVolumeProper=true; CryptoMigrationOn=false; GlobalPermissionsEnabled=true.
Both were mounted and unlocked after completed in-place APFS encryption.
For BOTH volumes, direct Foundation queries at the volume root return:
- NSURLVolumeUUIDStringKey: the correct UUID for the respective volume (omitted here for privacy);
- NSURLVolumeURLKey: the same volume-root URL as queried;
- NSURLVolumeIsEncryptedKey: present, explicit false (__NSCFBoolean, description 0).
The canonical mount path and diskutil volume identity match. This is not an inquiry against a parent volume, a missing key converted to false, or an inferred mapping based only on a display name.
Minimal read-only observation procedure, describing the existing successful queries (not rerun for this request):
- Select the already mounted APFS volume root and verify its UUID against diskutil.
- Construct a fresh NSURL using fileURLWithPath for that root.
- Query resourceValuesForKeys:error: for NSURLVolumeUUIDStringKey, NSURLVolumeURLKey and NSURLVolumeIsEncryptedKey.
- Compare the returned UUID/root URL and explicit encryption Boolean with the recorded diskutil fields.
The successful queries used Foundation through JavaScript for Automation's Objective-C bridge, in separate helper processes. An equivalent full Swift application runtime result has not been established. A separate failed JXA enumeration attempt is excluded from the evidence. We understand URL resource values may be cached; caching has not been established as the cause.
Expected: an encryption indication consistent with the completed APFS encryption, or documented semantics explaining why these indicators differ. Actual: explicit false on both volumes.
Questions:
- Are there documented limitations or known issues for this property on external, mounted and unlocked APFS volumes encrypted in place?
- What does false mean when the recorded diskutil encryption fields are positive? Is any additional read-only evidence necessary to interpret it?
- Which supported public read-only API and validation procedure should an application use to establish completed APFS volume encryption without weakening its policy?
- Could the observed behavior be affected by accessing NSURL resource values through the JavaScript for Automation Objective-C bridge rather than directly from a native Swift application?
We are requesting interpretation of existing evidence. No further encryption, lock/unlock experiment, drive modification or application build was performed for this inquiry. No credentials, private paths or customer data are included.
Thank you.
Hmmmm, the last time someone mentioned JXA in a context like this it was because they were running their code via some third-party tooling, and that tooling was using a custom sandbox. Apple doesn’t support custom sandboxes, as I explained on that thread.
If you put this same code into a standard command-line tool and run it from Terminal, does it exhibit the same problem?
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"