applescript saved as application doesn't run; strange workaround

I can read. One does not normally dive into an AppleScript application bundle to run the executable. Either of the following will run the AppleScript application (in the following case, an AppleScript/Objective-C application) in the Terminal. It would do so if the application were pure AppleScript too:

open ~/Desktop/rtn_email.app

osascript ~/Desktop/rtn_email.app

I have written hundreds of AppleScripts and those that have been saved from Script Editor as script bundles, or applications, just work with a double-click from the Finder.

Are you creating new scripts by using anything from the File menu : New from Template… sub-menu?

Apple's hearts may not be into Applescript any more ... SAD. Fired Sal, Applescript Evangelist.

May want to write an applescript to set the bit. Let's you drop something on app's icon and proceed from there.

 (* 
  Demonstration of how dropping files on AppleScript icon works.  Shows how to debug via on run path. Shows items added to folder.
  
 Save as an Application Bundle.  Don't check anything.
 
 Shows log statement.
 
 It is easier to diagnose problems with debug information. I suggest adding log statements to your script to see what is going on.  Here is an example.
	
For testing, run in the Script Editor.
	1) Click on the Event Log tab to see the output from the log statement
	2) Click on Run


Author: rccharles

 *)


-- Gets invoked here when you run in AppleScript editor.

on run
	--  debug lines
	set desktopPath to (path to desktop) as string
	
	-- here is a log statment.
	log "desktopPath = " & desktopPath
	
	-- Be sure to select a file on your DESKTOP.
	set see to alias (desktopPath & "Picture 1.png")
	
	-- Simulate dropped items list.
	set dropped_items to {see}
	
	common(dropped_items)
	
end run


-- Folder actions.
-- Gets invoked here when something is dropped on the folder that this script is monitoring.
-- Right click on the folder to be monitored. services > Folder Action Settup...

on adding folder items to this_folder after receiving added_items
	
	common(added_items)
	
end adding folder items to



-- Gets invoked here when something is dropped on this AppleScript icon

on open dropped_items
	
	common(dropped_items)
	
end open



on common(dropped_items)
	
	-- Write a message into the event log.
	log "  --- Starting on " & ((current date) as string) & " --- "
	tell application "Script Editor"
		activate
	end tell
	
	
	log "class = " & class of dropped_items
	
	
	repeat with droppedItem in dropped_items
		log "The droppedItem is " & droppedItem & "; class = " & class of droppedItem
		
		display dialog "The droppedItem is " & droppedItem giving up after 3
	end repeat
	
	
end common

Ken,

When you save an AppleScript from Script Editor, whether script, script bundle, or application, it should already have the execute bit on in the default permissions when it is saved. You should then be able to double-click on that application and it will just run. I have never, in several years, had to venture into the application bundle and mark anything executable.

How are you attempting to run the saved application when it indicates that it cannot be opened?

I am running macOS High Sierra 10.13.6 (17G6030) with the Security Update 2019-002 applied. Did not prevent me from saving a display alert "hello!" AppleScript from Script Editor as an application, and double-clicking it to run in Finder. Works fine here.

I suggest that you reboot into Safe Boot mode (press and hold the shift key until the progress bar appears). Safe boot is much slower than regular boot, so be patient. Try creating the script again, and saving as an application. Even if that does not work, reboot normally, and repeat the application creation to see if it works normally after Safe Boot.

That was a great fix.

Bug!

R