{"id":31306,"date":"2021-01-13T15:32:15","date_gmt":"2021-01-13T20:32:15","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=31306"},"modified":"2021-01-14T08:52:38","modified_gmt":"2021-01-14T13:52:38","slug":"lost-persistent-applescript-properties","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2021\/01\/13\/lost-persistent-applescript-properties\/","title":{"rendered":"Lost Persistent AppleScript Properties"},"content":{"rendered":"

Shane Stanley<\/a>:<\/p>\n

\n

Native code for Apple silicon Macs has a new, inviolable, requirement: it will not run unless it is code-signed. In practice, that means all universal apps have to be code-signed.<\/p>\n

[…]<\/p>\n

Script Editor running on Big Sur will produce universal applets. This will be the case on both Intel and Apple silicon Macs. So every time an applet is saved in Script Editor while running Big Sur, it will be signed to run locally.<\/p>\n

This signing will be noticeable in two ways. First, saving will be a little slower — signing takes a certain amount of time. Second, because the point of signing code is to ensure its integrity, and because the whole applet is signed, the applet will only continue to work as long as it is not altered after signing. And the normal persistence of property values — where you change a property’s value and the change is reflected the next time you launch the app — works by modifying the contents of an applet.<\/p>\n

So properties will not persist in universal applets run under Big Sur.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n