Posts

Post not yet marked as solved
12 Replies
Hi XMI- Radar filled for every single bug yes (still marked as open)- No change on beta 2, every bug still there
Post not yet marked as solved
12 Replies
Some more findings :- Your screensaver needs to be signed/notarized, while you can override on install an unknown developper build, it will error out again every time you open System Preferences- legacyScreenSaver is a sandboxing mechanism ! So if you ask for cache paths, you'll get this :localCachePath : ["/Library/Caches"]userCachePath : ["/Users/glouel/Library/Containers/com.apple.ScreenSaver.Engine.legacyScreenSaver/Data/Library/Caches"]The first one looks weird ? I'm unfamiliar with sandboxing, anyone with more info please chime in. Using the second one works, files are located there as expected, I don't think the first one is usable ?- Preferences also are located in that container (/Preferences/ByHost/ instead of /Caches in previous url)This breaks my workaround for Xcode to compile my screensaver's control panel as an app in a window, and breaks update path for settings for customers migrating from Mojave to Catalina.Some more stuff,- I can confirm that we are only called once in multiple monitor configuration (you used to get called once per screen). For some reason it's on my secondary screen, main screen doesn't get the view init. - I can also confirm that we are called that one time with the preview flag on which is not nice.
Post not yet marked as solved
12 Replies
Yes, I'm seeing the exact same thing. Looks like legacyScreenSaver is now running our .saver files and I haven't seen anything in documentation about a new API or anything specific about changes.Some other things I saw here with Aerial :- /Library/Caches/Aerial and ~/Library/Caches/Aerial are now the same thing (and the cache got wiped on update, which is I guess expected)- Looks like you can install a screensaver for all users still, I'm not sure where the file go then if /Library is locked down (there's a session about the new system lockdown later this week that will probably clarify this)- Loading a nib from my .saver bundle (for the preference panel) crashes a thread in systemStill early here, hopefully there are workaround for these issues.Any clarity on changes for screensaver would be truly helpful !(tried to reply to you yesterday but my message was in moderation limbo since !)