Where is this AppleScript gibberish bug being tracked, if it is actually being tracked?

https://discussions.apple.com/thread/254514861


@brympton writes:


“I think I am experiencing the same problem although to be specific this only occurs in automator with the Run AppleScript or Run JavaScript library items. In a new or populated script I start typing and after a few words get 3 periods automatically entered and/or the cursor jumps to a different location.”


It looks like it's trying to autocomplete, but failing. It has a life of its own. I'm writing an AppleScript inside an Automator QuickAction.

iMac (2017 – 2020)

Posted on Dec 6, 2023 11:03 AM

Reply
Question marked as Top-ranking reply

Posted on Dec 6, 2023 2:10 PM

This text entry issue in a Run AppleScript action has been ongoing for several releases of macOS now. Not just in Automator, but also in Shortcuts. I have filed a bug report early on with Apple and apparently it was ignored.


My workaround is to ensure that all the AppleScript code that I enter is done in Apple's Script Editor first, and after I compile to catch syntax, but not necessarily runtime issues. Then, I copy/paste that into the Run AppleScript action and click its associated compile hammer icon. Life is too short to try to power your way through the auto-injected … nonsense.


And, where I can get the coding job done without AppleScript, I avoid it like the plague, or incorporate it into functions (osascript) in a Run Shell Script with the Zsh shell.

Similar questions

1 reply
Question marked as Top-ranking reply

Dec 6, 2023 2:10 PM in response to Doug Parker, AAPL

This text entry issue in a Run AppleScript action has been ongoing for several releases of macOS now. Not just in Automator, but also in Shortcuts. I have filed a bug report early on with Apple and apparently it was ignored.


My workaround is to ensure that all the AppleScript code that I enter is done in Apple's Script Editor first, and after I compile to catch syntax, but not necessarily runtime issues. Then, I copy/paste that into the Run AppleScript action and click its associated compile hammer icon. Life is too short to try to power your way through the auto-injected … nonsense.


And, where I can get the coding job done without AppleScript, I avoid it like the plague, or incorporate it into functions (osascript) in a Run Shell Script with the Zsh shell.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Where is this AppleScript gibberish bug being tracked, if it is actually being tracked?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.