I have started a new thread because it seems when you notarise your apps for macOS10.14, it can break some things. Oh boy …
These are the two things I noticed - more may follow.
- Creating a declare is more piccy. For example you can not use libobjc.a.dylib anymore.You need to use Cocoa instead.
- The below code will not work anymore. It’s code to reveal a file in the Finder.
dim a as AppleEvent = New AppleEvent("misc", "slct", "com.apple.finder")
a.FolderItemParam("----") = f
If a.send then
a = New AppleEvent("misc", "actv", "com.apple.finder")
If a.send then
Maybe it needs an entitlement like in a Sandboxed app? Will do some test later.
BTW this script does work when I do not notarise the app. So it has nothing todo with the new way of Mojave dealing with permissions.
- AppleScripts do not work at all (I use AppleScriptMBS).
The AppleScripts I tried do refer to Finder. So maybe there is a new entitlement needed to use the Finder ?
Here an excerpt from the documentation on the “–option runtime” flag (which requires macOS 10.13.6 or Mojave).
So any declares MUST now access the framework (not dylibs directly) that Apple declares is the most appropriate.
Sadly it now means that macOS 10.13.6 or newer must be used to deploy apps, and as I’m halfway through a project there isn’t a hope in hell that I’ll update my production machine to High Sierra or Mojave (until at least 10.14.3 or even 10.14.6), see how it goes. So looks like I’ll be using a second machine to deploy apps.
Removing a file, see one of my xDevMag articles where I write up how to delete files in the macOS, with the option to move them to the trash, so the user can recover them. I forget which edition.[/quote]
As far as I know it is only possible to remove a file with the Finder AND keep the ‘Put Back’ feature enabled/working.
I have yet to find a different solution for this.