Thanks. I might be able to find a better way of handling the requirement e.g. a browser-specific script.Cheers.

Update: Using tccutil I have reset all permissions on a test laptop (tccutil reset all) and specifically the Desktop folder access (tccutil reset SystemPolicyDesktopFolder). But, re-installing my applet does not trigger any folder access permission requests or errors with UnZip.I'd rather not have to create a VM for this at present. Is there another way to set up a Catalina install so that I can see all permission requests ?Thanks.[Many thanks for all this. Yes, that seems highly likely to be the cause. At least one user did have the error on a clean install. When run for the first time, the applet does generate a collection of Automation and Accessibility permission requests. But, I don't remember seeing any permission request regarding the Desktop or any file/folder access. I shall go through the WWDC session you've linked. I generally use tccutil to clear out permissions but a VM is much more rigorous.Cheers.]

Thanks again. A VM is a bit much for me at present as it will have to be installed on a patched Mac – I don't have a Mac which is supported by Catalina.Anyway, I did another "tccutil reset all", deleted FFmpeg (from /usr/local/bin), created a new user, logged into that user, started the applet and UnZip installed FFmpeg without error. There was no request for permission to access the Desktop folder. Perhaps running on a patched Mac is changing how Catalina handles this situation especially as SIP is disabled. But, the Automation and Accessibility permissions are fully enforced and it would be odd for just one kind of permission not to be enforced, surely.One user definitely did have the "Files and Folders" permission dialog, they clicked on OK, and UnZip still caused the "Operation not permitted" error. That might be due to the shell commands not being blocked by the permission request (despite what Apple engineers said at the WWDC). Also, I've found that Accessibliity permission requests do not halt the applet which continues on to report an error because it can't use GUI scripting.Without being able to trigger the error on my Macs, I'll just take a couple of pokes into the dark: first will be to broaden the existing Try block to trap all errors and second, to issue a chmod on the downloaded Zip files to make sure the user has all the file permissions they need before Unzip runs.UPDATE 13/3/20: Also, have decided to download the zip file to usr/local/bin. That avoids the question of Catalina file and folder permissions all together.Cheers.

I found the answer which was simple: open the Service in Automator and choose "Other" in the application drop down box to add other applications. I now have the Service restricted to 5 web browsers.

UPDATE: OK, I found an image elsewhere in SwiftUI documentation that shows the required code. Monkey see – monkey type. So, now I understand what a stroke is !

what are you doing that risks corrupting the workflow declaration file? I'm not sure what might happen but, I am wary of "3" because the raw workflow file contains a lot of XML code I don't understand. Option "4" seems less risky as long as Automator doesn't delete the file. Also, in AppleScript, it's a bit quicker to get the entire contents of the file rather in "3" which would require code which parses the content looking for the version number. I've done test code for both and found "4" a little bit easier.

OK, I tried using automator actions to add the variable to the wflow file. I tried with "Get Specified Text" which I had hoped would pass the value to "Set Value of Variable". Automator said the value of the variable versions was "1.21" which was good. But, in fact the value was not stored anywhere near the variable in the xml file. Instead there is a mass of UUID and RTF data sprinkled in many places. Anyway, I tried your code but, it produced an error: Can't get value of {identifier:"com.apple.Automator.Variable.Storage", |name|:"Version", UUID:"844A34DE-EEA4-48B1-B56C-4941A4510522"}.) So, I'll try another day. Thanks. p.s., I've just found the "variables" pane in Automator Library. Maybe I'll try that. cheers.

It's working. Many thanks.

Many thanks for looking at this. I suspect the problem is with my "strings" files. A while back I had a problem in Script Debugger which, on compiling my applet, removed my custom icns file (Script Editor does that too) and removed the entire "en.lproj" folder. I was advised to rename the custom icns file and to rename all the localisable strings files. I did that. SD now compiles my app normally. More recently, I added French localisation. I think that's why French does not appear in the "Apps" pane – macOS is only looking for strings files which have the default name "localizable.strings". My guess is that macOS has already registered the other three languages and leaves them in place even though I've renamed the strings files. I have tried testing that hypothesis by renaming all the strings files back to "Localizable.strings" and compiling in SD. So far, French still does not appear in the "Apps" pane, although, I don't know how long to wait for the new localisation to be registered (perhaps I have to reboot). The "Apps" pane is weird. I have deleted my applet from the "Apps" pane then added it back. Before adding it back, I can see French is registered: But, after clicking on "Add", the applet is added but French is not shown.

Good advice, many thanks. I'll do up a VM or two to help test my applet in various versions of macOS. Currently, I can test cleanly only in 10.13 and 10.14. I had thought adding an app to the "Apps" pane would add the specific copy chosen – I used the "Other" menu item to locate the copy I wanted to add. But, I think you are right about the risks of having multiple copies floating around. Cheers.

+1. Yes, macOS 12.3.1 seems to have fixed my original problem. I've already changed my AS code from Finder to System Events – which is usually quicker than Finder anyway. Think I'll leave it there.

Sorry, should have posted to Apple Support Communities.

I'm having the same problem. I created a fresh, vanilla plain text file in TextEdit. Then ran this code: set open_this to "MyMac:Users:MyHome:Desktop:MyTest.txt" tell application "Finder" to open open_this I get this error: "The document "MyTest.txt" could not be opened. You don't have permission. To view or change permissions, select the item in the Finder and choose File > Get Info" So, I switched to this code: set open_this to "/Users/MyHome/Desktop/MyTest.txt" tell application "System Events" to open file open_this That produced a new error: "The document "/Users/MyHome/Desktop/MyTest.txt" could not be opened. The file does not exist." This seems to be a variant of the bug in macOS 12.3 which prevented using Finder to open files from within AppleScript. Switching to system Events was a workaround but now, even that is not working.

This behaviour seems not to occur in macOS 12.4 beta (Build 21F79). Not sure it has been fixed in all situations.

Yes, many thanks. It's good to know I'm not the only one caught out. It leaves me wondering: is it possible to create a Ventura beta install drive ? If so, how ? I can't find the Ventura installer anywhere. Also, is there a way to get the Ventura beta into a VM ? I've tried but my Parallels VM refuses to sign in with my Developer Apple ID. How are we expected to test betas if we can't install them safely ? I have sent Apple a (polite) roast via "Feedback Assistant". Maybe someone will read it.