“Full Disk Access” and “Control the Computer” didn’t make a difference. Which I actually think is good - because really those two settings shouldn’t affect anything for a regular app.
Yes, the app is 64-bit.
Ok I will submit this issue as a severe bug to Apple shortly then.
The problem actually starts right after signing the app (that is, before the actual notarization).
I’m signing the app with a AppleScript droplet.
I also have a separate target with auto-signing enabled. There’s no problem when running the app produced through this target.
So the issue is somewhere with the signing droplet. I’m pretty sure it worked flawlessly before - that’s why I didn’t even care to test the app after the signing stage at this point.
Will work on it.
As a side note. I think Apple should give us a more specific error in cases where Apple Events authorization dialogs are being suppressed for whatever reason - instead of just generic “Not authorized to send Apple events…” on any occasion.
In the codesign command, I need to include a path to entitlements file where the com.apple.security.automation.apple-events key is set to YES.
–entitlements path
Once I added this to the signing droplet, all seems to work as expected.
As to SD Notary, it’s a great tool, thanks Shane - but I just need all kind of custom options for my workflow, that’s why I always have to build my own tools. dmg creation, naming convention, custom installers etc.
I did build my notarization app - well hopefully it’s the last piece of the puzzle!
I wonder if you use the entitlements file in your codesign script? Not sure how I missed this requirement and if it’s always needed at all.