The good news is Sonoma finally fixes the bug where the icon for a third-party screensaver wasn't using the retina asset.
The bad news is that Sonoma has also broken all third-party screensavers, including the one I made for a children's cancer charity fundraiser.
If somebody could look into this bug, that would be most appreciated:
FB13003899
@jamesthomson I don’t know if they pay much attention to 3rd party screensavers.
They broke key input a few releases ago and have yet to fix it.
There are legitimate reasons to accept key strokes in screensavers.
@jeff They keep changing things, so it's not like they’re not working on the stuff, but yeah…
@jamesthomson. I wonder if 3rd party screensavers will have the option go be used as a wallpaper (and work like Apple ones)
@afastaudir8 That would be nice, but I'll settle for them just working at all for now!
@jamesthomson do you happen to know if Aerial works? I assume not based on our comments.
@javier No, it didn't work either, I'm afraid. But I'm hearing there might be a fix in the works, so we shall see.
@jamesthomson Crossing fingers. Thanks.
@jamesthomson I‘m missing updated documentation the most: about sample code, sandboxing (are they?), notarization (relevant?), frame being broken sometimes for 2nd display, logging to console… not easy for a starter