They now get signed, an Info.plist is embedded, they’re notarized by Apple, use the hardened runtime, maybe the App Sandbox, and request entitlements. So how do you check their version?
It’s all too easy to lose all previous versions of a document: one false move to another volume, to iCloud, or shared over a network and they’ve gone. How can you preserve them?
Document versions, accessed through Revert To…, are a major part of the protection macOS provides for dealing with errors. How to get the most from them.
Every time you save a file or build in Xcode, changed source files are added to the version database. Use this powerful tool to go where backups and Git can’t.
Which of the cluster of hidden files and folders at the top level of an APFS volume should be preserved or copied to a copy of that volume?
Although problems are rare, solutions are very limited. How to test the version system, and the few things you can do to fix it.
Bridging the gap between Undo and backup, its a major productivity feature implemented using a hidden folder at the top level of each volume.
Where to see them, how they’re constructed, Apple’s rules, how they are created, and how even Apple doesn’t use them according to its own rules.
Users need to know what changes in each update to macOS, as it may fix existing bugs and introduce new ones. Here’s how I work out what has changed, and its limitations.
I was wrong: the first proper update to Big Sur is version 11.1, and next year we should be grappling with macOS 12.