App signatures are only checked on app first run – it may once have been true, but is no longer accurate. But can you bypass those additional checks? Is this a vulnerability?
First full release version, which conforms to macOS clearance convention, and lets you know which flags it has changed.
How this occurs, why, and what to do to manage the problem when it affects you. Complete with a visual summary and references.
Try using this workaround: it requires quick actions, and despite Apple’s promise, it only works until you next save the document.
How a security feature trying to block malicious documents has rendered a Finder feature useless, causing users and developers problems.
Two sets of log excerpts demonstrate how macOS can prevent a user from opening a document, then mislead them into thinking it’s the app at fault.
You double-click to open a document, and see a security alert telling you it’s from an unidentified developer and your security settings prohibit opening. What the hell?
Repairing LaunchServices database, rebuilding it from scratch, and controlling individual app entries – all using this undocumented command.
Sometimes macOS decides you want to open documents using the wrong version of the right app. Here’s how to fix that.
How can the Open Recent menu offer to open a document that no longer exists when the volume it was on is no longer mounted?