I am also seeing this issue. We use sudo for the same reasons. We also noticed ps(1) is failing too. I have a forum post about this as well.
Post not yet marked as solved
@fschilling - Question: are you calling su and ps and other utilities directly from 'postinstall', or are you running a second sh script that calls those utilities? I am doing the latter.
Post not yet marked as solved
Thanks for your reply, fschilling. I took another look at my log and I also see 'ps' failing !!! This command is nowhere near as risky as 'sudo', so something is definitely wrong here.Feb 20 10:50:22 sqa-macpro-1 package_script_service[784]: ./postinstall: mac_do_postinstall.sh: line 199: /bin/ps: Operation not permitted
Post not yet marked as solved
Adding some clarification:In case anyone was wondering why we need "sudo" for copying files into place:We are running our installer with admin privileges and we are using “sudo” so that we can run certain operations as the current user instead of with the current installer elevated privileges. In other words, we use sudo to make sure files are owned by the current user, and not that admin user.
Post not yet marked as solved
I've been getting this again recently, last night two builds failed because of Error code 239 when using altool to check notarization-info. It seems to fail more at night than during the day?
Thanks a lot for confirming that. And my QA colleague did also notice the online mechanism is not working consistently. It worked on 10.14.6 beta but failed on 10.14.5 for one machine and then worked for another 10.14.5 machine. Apple's stuff is definitely broken!Cheers
That's correct. If the machine has access to the internet, it should be able to validate (assuming that mechanism is not also broken today)
It's at least reassuring that I'm not the only one seeing this!
My notarization automation failed last night during the stapling step.Despite a successful notarization (confirmed via e-mail and with altool --notarization-info) I am seeing the follwing from stapler:The staple and validate action failed! Error 68.I am using 10.14.4 and XCode 10.1 to staple. This was an issue in 10.13.x that was supposedly fixed in 10.14:You can resolve a few common stapler issues by upgrading your tools. In particular, if you see error -68 on macOS 10.13.x, you can resolve the issue by upgrading to macOS 10.14 or later. Alternatively, run the following command once to clear the Valid cache:$ sudo killall -9 trustd; sudo rm /Library/Keychains/crls/valid.sqlite3It sounds like a regression to me. I am waiting for Apple to say something or fix it.It's also worth mentiong that I can still staple bundles that were notarized yesterday and earlier. Has anyone else tested stapling (or 'exporting' as I believe it's called on the GUI side) previously notarized bundles?
Post not yet marked as solved
Thanks for replying. Have you tried command line tools? Do you get any text output from the export attempt. I wonder if we're having the same issue. I'm attempting to notarize again and get new RequestUUID's hoping this was a random fluke.
