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

"You cannot use the Aerial screen saver with this version of macOS." #567

Closed
dennisN75 opened this issue Oct 22, 2018 · 9 comments
Closed

Comments

@dennisN75
Copy link

I got still the same problem with the error message.
I use Mac OS 10.3.3 and can see in the preview the error message.

I tried different versions, also the newest beta 4.

What can I do?

@glouel
Copy link
Collaborator

glouel commented Oct 22, 2018

@dennisN75 Per the troubleshooting section, this is a bug in your macOS version, there's a workaround though:

"You cannot use the Aerial screen saver with this version of macOS." error: Select Aerial, close System Preferences with Aerial still selected, re-open System Preferences and Aerial should now work. This is a known bug with Swift screensavers in macOS/OS X reported to Apple as rdar://25569037.

This was fixed by Apple in later 10.3.X releases.

@dennisN75
Copy link
Author

I saw this workaround but it doesn't work.

@dennisN75
Copy link
Author

And i had a typo in mac version. Of course i have 10.13.3

@glouel
Copy link
Collaborator

glouel commented Oct 22, 2018

Yeah I figured it was 10.13.3.

I'd highly suggest you update to .4 or .6, it's a macOS bug with Swift screensavers, nothing we can do about that one. There were many issues at the time of their release, it looks like it started getting fixed in 10.13.4. It's definitely fixed in 10.13.6. This also happened on Mojave beta (thankfully fixed there too).

See this issue here for example : #377

Enabling the clock (at the bottom of the System Preferences) was another workaround around that time, worth a shot although I think it was another bug.

@dennisN75
Copy link
Author

dennisN75 commented Oct 22, 2018

Ok thanks. Then i will update.

@glouel
Copy link
Collaborator

glouel commented Oct 22, 2018

Try enabling the clock first, but yes you should defintely consider updating.

@dennisN75
Copy link
Author

enabling clock doesn't work.

@glouel
Copy link
Collaborator

glouel commented Oct 22, 2018

Ok was worth a shot ! Sorry about that, OS update will fix this for you.

@glouel
Copy link
Collaborator

glouel commented Oct 23, 2018

Closing this, please reopen if you still have an issue.

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

No branches or pull requests

2 participants