{"id":27861,"date":"2020-01-14T20:21:44","date_gmt":"2020-01-15T01:21:44","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=27861"},"modified":"2020-01-24T15:27:10","modified_gmt":"2020-01-24T20:27:10","slug":"aerial-screensaver-and-catalina","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2020\/01\/14\/aerial-screensaver-and-catalina\/","title":{"rendered":"Aerial Screensaver and Catalina"},"content":{"rendered":"

Guillaume Louel<\/a> (via Tanner Bennett<\/a>):<\/p>\n

In macOS Catalina, 3rd party screensavers are now running in a sandboxed container which limits everything. As of right now there are no workarounds for many of the restrictions.<\/p>\n

[…]<\/p>\n

Aerial can only write<\/strong> in the legacyScreenSaver.appex sandbox container, which means in Catalina, JSON files and videos can only<\/strong> be downloaded in ~\/Library\/Containers\/com.apple.ScreenSaver.Engine.legacyScreenSaver\/Data\/Library\/Application Support\/Aerial<\/code>. Aerial can still read (only) the rest of your system disk so you can still store the videos in another folder after they are downloaded by manually setting the Cache. But Aerial cannot download videos to this cache.<\/p>\n

[…]<\/p>\n

Your cache may be wiped by the Catalina installer<\/p>\n

[…]<\/p>\n

[Because] a screen saver is not an app (we are a plugin run by legacyScreenSaver) we can’t ask for entitlements for, say, accessing filesystem.<\/p>\n

[…]<\/p>\n

Some (not all) of Apple screensavers are now bundled as an .appex<\/code> too, with their own permissions. As far as I know that format is still not documented to this day nor available to 3rd parties.<\/p><\/blockquote>\n\n

Previously:<\/p>\n