I'm distributing my app in zip format. But stuck in app update? My app self-detects for the latest version. If yes, then launch other non-appsandbox app that download the latest version, and then replace the old app (in the /Applications directory) with the new one. It works correctly. But once I made the Updater app a Sandbox app, it did not allow me to replace the app. Error: You don’t have permission to save the file “ESPlus” in the folder "Applications.”
You don’t have permission to save the file “ESPlus” in the folder "Applications.”
Right. A sandboxed app starts with a default static sandbox where the /Applications directory is readable but not writeable. For more on this, and macOS’s file system permissions in general, see On File System Permissions.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
Thanks for your quick ans but then what is the way to update notarized app distributed to outside the MAC Appstore in .zip format?
what is the way to update notarized app distributed to outside the MAC App Store in
.zipformat?
If you distribute an app directly, rather than on the Mac App Store, you take on responsibility for updating it. Some folks build their own update mechanism — the obvious player here being Sparkle — while other just ship a new version and expect the user to do the update.
In terms of sandboxing, directly distributed apps don’t have to be sandboxed and thus can get around this restriction. If you want your main app to be sandboxed then it’s common to ship a non-sandboxed helper program to do the upgrade. This is especially important if you want non-admin users to be able to upgrade, because /Applications is only writable by admin users, and thus you have to escalate BSD privileges.
Some background reading here:
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"