Hi,
We are starting to see issues where installing locally via the payload file and postinstall.sh works fine but installing it after being packaged (either via Packages or PKGBUILD) results in the following error when launching the application (Pro Tools 2023.3.0 as an example here)...
' "Pro Tools" is damaged and can't be opened. You should move it to the Bin.'
Following the help icon opens a page stating, "The app has been modified, and its code does not match the original signed code."
In Privacy and Security we can go ahead and choose to "Open Anyway" but this is not a viable way forwards for applications that we are trying to deploy hands-off.
It feels like the packaging process is stripping some attributes from the files. I have tried to use xattr to re-add "Date Downloaded" data but that doesn't resolve the issue.
In the case of our Pro Tools 2023.3.0 package, it copies a DMG to /tmp (we've tried other areas in case this was the problem and we're trying this way due to the problems we've encountered), mounts it and runs the following command...
installer -verboseR -pkg "/Volumes/Pro Tools/Install Pro Tools 2023.3.0.pkg" -target /
Which confuses me, in this instance, why it's creating a problem as, even if any attributes are being stripped from the DMG, it shouldn't affect the PKG inside it, should it?
I've seen a similar thread where someone said (about another app) "just use the App Store version" which isn't a fix for all packages, obviously, and we're looking for a general fix for this issue.
Any help would be gratefully received as this has us really stumped...
Thanks
Stuart
