Another post thanks to Many Tricks' Peter Maurer; this particular bug bit me last night—I spent 30 minutes trying to figure out why a compiled AppleScript with a droplet wasn't working. I never did get it, so I emailed Peter, and he pointed me to these tweets from a while back…
…which means the app won't launch. You have to "chmod +x applet" manually to make it work.
— Peter Maurer (@petermaurer) March 14, 2017
And yea, that was the problem: As soon as I added the +x to the compiled script, everything worked as expected. The exact syntax is:
chmod +x /path/to/compiled.app/Contents/MacOs/droplet
I'm documenting this here so that I can find it more easily the next time I save a compiled droplet AppleScript and forget about this not-so-little bug.
This confuses me. I hadn't noticed this issue and I'm running 10.12.4, so I opened the following in Script Editor, saved it as an application, and had no problems dropping a folder to make a disk image on the desktop. Is there a chance that security hacks i've implemented (system integrity and Gatekeeper) are preventing the issue you describe?
Should've quoted the script somehow, apparently the blog messed it up. It may be easier for you to fix than for me.
Seems that tabs were changed rather than omitted and quotes were smartened.
Anyway, the point is that I have Script Editor 2.9, but I have no such problem. Any idea why?
Sorry, haven't had time to try it yet - just reformatted it earlier. Will try to look at bit later tonight and see if it works for me.
-rob.
Comments are closed.