{"id":51392,"date":"2026-03-27T17:23:55","date_gmt":"2026-03-27T21:23:55","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=51392"},"modified":"2026-03-27T17:23:55","modified_gmt":"2026-03-27T21:23:55","slug":"macos-26-4s-script-editor-wont-open-some-older-applescripts","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2026\/03\/27\/macos-26-4s-script-editor-wont-open-some-older-applescripts\/","title":{"rendered":"macOS 26.4’s Script Editor Won’t Open Some Older AppleScripts"},"content":{"rendered":"

Adam Engst<\/a>:<\/p>\n

\n

Allen Gainsford first reported the issue<\/a>, noting that many of his BBEdit AppleScripts no longer worked after upgrading to macOS 26.4. Attempting to run them produced macOS error code -1758<\/a> (errOSADataFormatObsolete<\/code>)[…]<\/p>\n

Further investigation by Dafuki revealed a nuanced situation<\/a>. In his testing, many AppleScripts—even some dating back to 2006—continued to run without issues when triggered from apps like BBEdit and Keyboard Maestro. However, others wouldn’t open, and after failing to open one script, Script Editor would then refuse to open any subsequent scripts until it was quit and relaunched.<\/p>\n

He found that the issue appears to involve older compiled scripts that rely on legacy storage formats—hence the “data format is obsolete” errors. Allen Gainsford even found that one affected script had a 0-byte data fork and a 26 KB resource fork, indicating that the actual script was stored in the resource fork—a legacy structure macOS supports only for backward compatibility.<\/p>\n

Although Script Editor’s 2.11 version number didn’t change from macOS 26.3.1 to macOS 26.4, Apple did increment its build number from 233 to 234, indicating that it received some changes.<\/p>\n<\/blockquote>\n\n

A workaround is to use the retired Script Debugger. I wonder whether osacompile<\/code> could also update the script’s format.<\/p>\n\n

Previously:<\/p>\n