I write scripts and push them to other users. Tahoe is a major pain. On some, but not all, Tahoe Macs this happens.
Every dialog gets a beach ball. It will last for 15 - 45 seconds, and start over for every user action, like type a single character or for every selection in a multiple select list.
Scripts are signed. No difference if they are notarized or not. It happens on some Macs, but on very similar Macs same script run just fine. No problmes anywhere when run from Script Debugger/Editor.
It is the environment, like TCC or some other dark whichcraft.
Some scripts are extremly simple, like 30 lines of code: ask user for a job name with display dialog, then use mkdir to create a set of folders with pre-defined names.
Example:
–start:
tell application “Finder” to set thisFolder to (target of window 1) as alias
set zetarget to POSIX path of (thisFolder as string)
set rootName to text returned of (display dialog “Job number and name” default answer “000000 my job”)
… at there goes the beach ball.
It is neither an xattr nor permission thing. What should I do to troubleshoot this?
[I use Sequoia to make the scripts. But as I said, they run just fine some Tahoe macs.]
I would start with measurement in an attempt to identify the cause of the SPOD. Use Activity Monitor to get a Sample report of your script’s process while it is hung.
If you don’t know how to read a sample report, post it here or use AI to interpret it.
Based on a similar experience I had, I’m going to assume you are not building the script(s) in Tahoe. You’ll have to save all scripts FROM Tahoe in order for Tahoe users to not be affected by the slow dialogs.
There apppears to be no backwards compatibility issue however - saving the script in Tahoe and pushing to someone with a previous OS does not result in slowdowns.
One small addition to this thread: with some complicated scripts, it makes sense to build the scripts in Tahoe but notarize them from Sequoia.
Some of my scripts, if my notarize them in Tahoe, complete notarization but then trigger the “Move to the trash?” message when started.
I know I can eventually work out which entitlements, etc., to use to avoid this, but, meanwhile, it’s easier to notarize them from Sequoia, which works correctly every time.
Should I also save libraries again in Tahoe and push them too? And should I code-sign them?
But it is not consistant; When I try on some Tahoe test-macs my scripts from Sequoia-compile works just fine without slowdown. But “after a while” (an hour later) they too become slow. This is just strange.