-
Notifications
You must be signed in to change notification settings - Fork 31
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
Not working in Sonoma 14.4.1 #73
Comments
"screen will just turn black" sounds like macOS has saved you from using a macOS program from a developer like me that not pays apple 99 USD annual fee so that it program just works for any user. Please send some regards to Tim Cook that he did this protection for you as a user and for more regular revenue of Apple and its share holders. Apple changes the way a normal user can allow certificates of developers that not pay the 99 USD a little bit with each major OS update and hide the stuff better and better to force those developers to pay them the regular fee. I already documented how to enable the Screensaver for macOS Mojave and Big Sur and put it into the README, but Apple has managed to tweak it and change it again in Sonoma good enough that it is overseen by most users. 1st confirmation if you like to install is (for all users or just your user): 2nd and 3rd confirmation looked for me exactly the same (so I only upload one screen shot) and I have no idea why Apple like to inform the user twice in a row now? 😕 After those first 3 confirmations you end up with a black screen (still not allowed software to run) without telling the user that the execution was blocked and this is the reason the screen is black. It also gives you no hint where to look next if you still like to execute the program. Here you find the hidden 4th confirmation if you do it right after a fresh installation attempt. You need to scroll all the way down in this tab to section "Security" to even see it. But just hit the "Open Anyway" button is not enough at 4th confirmation. The user should be scared after pressing it and now the user even needs to confirm with his user password, fingerprint, Face ID or whatever your Mac uses. And if four confirmations and a fingerprint was not enough to scare the user away Apple uses a five attempt to save Tim Cooks revenues and ask for a 5th confirmation. |
Wow man this really sucks, i am a developer myself and felt every word you said. It really feels as if they want to take down free software. Thanks for the detailed explanation on how to get it working again! |
Btw. there are more problems with Sonoma and this program than just this. Some of your folders are blocked for the ScreenSaverEngine by the sandbox system. And to make it more confusing when the preview runs under System Preferences it has a different sandbox configuration, see here: #71 (comment) And just today I got aware of another macOS bug under Sonoma regarding that changes you did under System Preferences will be not used until you log out or reboot, see here: #74 I already committed a workaround that works form me fine on Sonoma: a34828a I plan on a new 1.55 patch just for this. But I need more time to test this before a release. |
I will gladly test it one of these days and let you know, thanks man |
The alpha version seems to work a lot better! |
The new version plus the instructions you provided do work much better. One thing tho, what was the trick again to make it work again when it stopped working and only shows a black screen?, i plugged some different monitors and changed some settings and suddenly it stopped working. |
This does not seem to work for me on Sonoma, no matter what i do. The screen will just turn black. Is there a workaround or a planned patch?
The text was updated successfully, but these errors were encountered: