It has often been assumed that App Store apps don’t undergo app translocation. That isn’t true: here’s an example of one that gets stuck in eternal translocation because it comes with an unwanted gift.
translocation
Launching an app for the first time used be simple. Now we have the SSV, launch constraints and app translocation to contend with.
Some apps have odd problems when they’re run in translocation. Here’s how to tell whether they are, and what to do about it.
Gatekeeper may decide to run a new app from a random location, in translocation. The rules for this are explained, and how to ensure that doesn’t affect your apps.
All apps now undergo Gatekeeper assessment, but only some have XProtect checks for malware, and the unfortunate few get translocated too.
Causes include code signature errors, app translocation, damaged documents, and corrupted or incompatible preference file.
If you thought that App Translocation only happens to apps left in their original folders and not moved, and doesn’t happen after first run, this could come as a surprise.
What and where is the Gatekeeper app or service? The answer is that it’s a collaborative system or technology to check apps and ensure that only trusted software is run.
There’s more to the quarantine flag, as it’s not binary on/off, and app translocation can trap even notarized applications if you don’t move them right.
You unarchive a freshly downloaded app and try to give it a test run. It immediately crashes. Here’s one common reason, and how to solve it very simply.