Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Level 6

12,333 points

"Press Run to run this script..." confirmation started appearing...why?

I've got a set of AppleScripts I run from Spotlight, and all of a sudden they run with a confirmation alert that I've never seen before. Upon launch, each of these scripts puts up an alert that says "Press Run to run this script, or Quit to quit." So I gotta hit a button before the script will continue running.

I did a web search on it, and they all said the same thing: You saved your script with the Startup Screen option on. But I didn't! They've been running headless for months, some for years, and none of them started displaying the confirm dialog until now. I even opened and resaved them with the Startup Screen option off (it wasn't even checked when I went to resave them) and they still do this.

I guess I'll try fixing permissions unless somebody has a better idea. As far as I can tell, I've done everything right.

Mac Pro, MacBook Pro, iPhone 3GS, Mac OS X (10.6.5), PowerBook G4 15" Al, PowerBook G3 FireWire, PowerCenter Pro, PowerBook 160

Posted on Nov 26, 2010 11:23 PM

23 replies

Jun 22, 2011 1:34 PM in response to fedeboraxx

Well, that seems to have fixed it for me. The control key was indeed the culprit. Thanks fedeboraxx!

res1233

Level 1

9 points

Jul 7, 2011 8:24 PM in response to Network 23

Incase anyone was still stuck, this seems to be controlled by the "spsh" resource in the .rsrc file in the application bundle. If the second bit of that resource is "01" then the dialog will show, if it's "00" it wont. Also keep in mind that the executable's name in the MacOS directory must be the same as the .rsrc file or none of the settings in there will matter. Usually this is "applet", however I'd check to be sure.

If there is something preventing access to this file, such as a permission conflict, it will act as if the file is not there. It's possible that some random program you have messed the permissions up on the .rsrc files, causing this to happen. Rather long shot, but it's all I can think of. You can try running "sudo chown $USER applet.rsrc" and then "chmod +rw applet.rsrc". If that doesn't do it, then I'm all out of ideas.

Jan 25, 2013 3:20 PM in response to res1233

This indeed corrects running scripts via Keyboard Shortcuts in Mountain Lion as well.

Jul 30, 2013 5:37 AM in response to res1233

I had this problem today with a script which had previously "just worked." Strangely, if AppleScript Editor were open, it worked fine. Close ASE, it doesn't.

I looked at the permissions on the applet.rsrc file and noticed that it wasn't marked as executable, so I added the "x" permission to it for everybody, and that solved the problem.

In terminal, change directories to the applet's Resources folder and then do:

chmod +x applet.rsrc

Hope this fixes the problem for somebody else, too.

Jul 30, 2013 10:31 AM in response to Bill Eccles

Bah. That didn't fix the problem at all. Thought it did, but... not.

ron-r

Level 1

4 points

May 8, 2014 11:15 AM in response to fedeboraxx

Bingo! Removing the Control key from the keyboard shortcut fixed my problem.

Jun 25, 2014 6:25 AM in response to ron-r

...or you could just let go the Ctrl key really fast 🙂

Feb 24, 2016 6:25 AM in response to fedeboraxx

GENIUS!!...Yes, that WAS my problem. It was going crazy. Thanks A LOT for the taking the time it post that....some 5 years ago. LOL...

"Press Run to run this script..." confirmation started appearing...why?