Back to the Mac - Installer tweaking....
-
So the outstanding problem I have with my Mac version of the installer is because of permissions, I need to install my plugins in:
MacintoshHD/Users/<user name>/Library/Audio/Plug-Ins/
Which is all fine - except on occasion the user, or their system, has finagled the permissions and my installer fails - and I get a support call - and have to walk the user thru setting the permissions on a folder that a goodly percentage of dont even know exists...
So I'd like things to be more like the Windows version of life - where the user has to accept the installer will be modifying their computer in some way - before the installer runs...
So I can install plugins in:
MacintoshHD/Library/Audio/Plug-Ins
Now there is such a thing on the Mac - where the app asks for the user permission (user name/password) - so I assume there's some system call to make this happen - or some config. for the app itself....
..and finally a question: has anyone worked out how to get to this state of nirvanah?
-
-
@d-healey said in Back to the Mac - Installer tweaking....:
https://forum.juce.com/t/osx-permissions-going-nuts-here-help/32116
https://forum.juce.com/t/elevate-rights-on-osx/32868/3
https://forum.juce.com/t/elevated-permissions-in-macos-or-so-we-thought-edited/55419Thanks _ I think.... those links seem to be a bunch of people being frustrated that they cant get it to work, however:
https://forum.juce.com/t/fr-add-music-files-network-client-sandbox-entitlements/32866
seem to suggest that JUCE has some additional sandbox enititelements added which includes this:
std::vector<std::pair<String, String>> sandboxOptions { { "Network: Incoming Connections (Server)", "network.server" }, { "Network: Outgoing Connections (Client)", "network.client" }, { "Hardware: Camera", "device.camera" }, { "Hardware: Microphone", "device.microphone" }, { "Hardware: USB", "device.usb" }, { "Hardware: Printing", "print" }, { "Hardware: Bluetooth", "device.bluetooth" }, { "App Data: Contacts", "personal-information.addressbook" }, { "App Data: Location", "personal-information.location" }, { "App Data: Calendar", "personal-information.calendars" }, { "File Access: User Selected File (Read Only)", "files.user-selected.read-only" }, { "File Access: User Selected File (Read/Write)", "files.user-selected.read-write" }, { "File Access: Downloads Folder (Read Only)", "files.downloads.read-only" }, { "File Access: Downloads Folder (Read/Write)", "files.downloads.read-write" }, { "File Access: Pictures Folder (Read Only)", "files.pictures.read-only" }, { "File Access: Pictures Folder (Read/Write)", "files.pictures.read-write" }, { "File Access: Music Folder (Read Only)", "assets.music.read-only" }, { "File Access: Music Folder (Read/Write)", "assets.music.read-write" }, { "File Access: Movies Folder (Read Only)", "assets.movies.read-only" }, { "File Access: Movies Folder (Read/Write)", "assets.movies.read-write" } };
so I think the pertinent one is this:
{ "File Access: Music Folder (Read/Write)", "assets.music.read-write" },
..any idea how I add this in projuicer?
-
-
@d-healey great I will try that.... it seems I might have to turn on Use App Sandbox - but hey that seems logical, now it would really be nice if we could have this as a HISE preferences setting..... pretty please @Christoph-Hart ???
-
@Lindon do I need use Hardened runtime too? Any one know? Otherwise its trial and error for me....
-
@Lindon said in Back to the Mac - Installer tweaking....:
@Lindon do I need use Hardened runtime too? Any one know? Otherwise its trial and error for me....
You should be using this any way when you codesign.
codesign --deep --force --options runtime...
-
@d-healey said in Back to the Mac - Installer tweaking....:
@Lindon said in Back to the Mac - Installer tweaking....:
@Lindon do I need use Hardened runtime too? Any one know? Otherwise its trial and error for me....
You should be using this any way when you codesign.
codesign --deep --force --options runtime...
oh, I am, I am....