Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"legacyScreenSaver" in Location Services Menubar #1149

Closed
Jimmbo opened this issue Jan 26, 2021 · 2 comments
Closed

"legacyScreenSaver" in Location Services Menubar #1149

Jimmbo opened this issue Jan 26, 2021 · 2 comments

Comments

@Jimmbo
Copy link

Jimmbo commented Jan 26, 2021

2018 Mac Mini
MacOS 10.15.7
Aerial 2.2.6

After activating screensaver, a location services icon apears up in my menubar to tell me Aerial checked my location. That's ok, I did give permission. But can't Aerial be identified as "Aerial" rather than "legacyScreenSaver"? This way sounds dodgy (plus the dodgy capitalization and spacing).

Screenshot

@glouel
Copy link
Collaborator

glouel commented Jan 26, 2021

In Catalina, Apple made a new screensaver API (for good reasons, the old one is a security risk), but didn't make it public. So for "old" screensavers, that includes 3rd party like Aerial, but also some Apple screensavers, they made a "bridge" called legacyScreenSaver.appex. That's what you are seeing here. I've been waiting for Apple to make it public so I can port Aerial to the "new" API, but that didn't happen yet, even with Big Sur.

This is why many features no longer work in Catalina and later (skipping a video by pressing right arrow key is the classic example).

Until Apple provides a better API, I can't change it, because it's literally how macOS works. Is it weird ? Yes, but I can't do anything about it. I did open many radars with Apple about it but so far, still nothing.

Side note, the name isn't dodgily capitalized, it's just how system stuff is capitalized. If you dig around screensavers, many other 1st party screensavers show up under iLifeSlidshows.appex

@Jimmbo
Copy link
Author

Jimmbo commented Jan 26, 2021

Ah, one of those things. Got it!

It's certainly not so bad from the user's end...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants