#89
Separate MobileGestalt backup reads from write diagnostics
On Watch6,14 running watchOS 26.6.1 (23U95), Backup MG can read the cache directly even when MobileContainerManager does not grant access. Try that read first, retain the existing fallback, and add a separate check for direct write access that only opens and closes the file.
Tested on a physical Series 8 (Watch6,14). The patched app created a 13,152-byte manual backup that passed plist validation and matched the original byte for byte. Both write-open checks returned EPERM.
Apple Watch Series 8 (watchOS 26.6.1, 23U95)
| Back Up Current MG | Manual backup in the library | Direct write-access result |
|---|---|---|
Thanks for separating backup reads from write diagnostics. We independently validated the read-first approach on a physical Apple Watch Series 7 (Watch6,7), watchOS 26.6.1 (23U95).
To be precise, this was a local implementation based on upstream 1.6.1, commit a4feb9071c2475cb25b54953ec60b368c054cd26. We did not check out or build this PR branch, so this is supporting device evidence for the approach rather than verification of the exact PR diff.
Observed results:
O_RDWR | O_CLOEXEC | O_NOFOLLOWprobe, without creation or truncation, returns EPERM (errno 1).Selected anonymized log excerpts:
This confirms that a failed write-access check should not prevent backup creation on this Series 7. It does not establish write access or native Hermès activation. The separate bounded write-access experiments are documented in #90.
No cache contents, backup files, account/device identifiers, personal paths, or full logs are attached.